Iptv Buff wrote:
> I am not getting zap2it guide since Sep16.
> in .kodi/addons/script.module.zap2xml/zap2xml.log I see this error
>
> 2017-09-25 20:24:30,497 Didn't Match .*Logout of your Screener account.* Sleep 1 sec.:Function: loginZAP :Line: 591
> 2017-09-25 20:24:31,500 Failed to login within ,3, retries.
> :Function: loginZAP :Line: 594
> 2017-09-25 20:24:31,500 None
>
> I logged into zap2it site via browser. That works fine.
> I restarted librelec. Same error.
>
> Any pointers/help?
The problem is, if you are using LibreELEC then you are not using the real zap2xml program, you are using someone's addon that is an adaptation of zap2xml. I use genuine zap2xml and I am not experiencing this issue. Unfortunately because LibreELEC doesn't give you access to the Linux command prompt, you can't install the real zap2xml from http://zap2xml.awardspace.info/ but if you could I would say start over by downloading the current version from there and reinstalling.
Because you are using someone's adaptation of zap2xml, you will not find help from the Zap2xml author and you probably won't find help at the Kodi site unless it is a thread specifically related to Libre/OpenELEC. You need to go to a LibreELEC support site or forum and ask there, because it's the author of the script.module.zap2xml addon that's going to have to fix this, especially if it's affecting multiple users. It's probably not a difficult fix but in the long run, if you can manage it, you'd be better off avoiding the *ELEC distributions just because you can't fix issues like this without waiting on someone else to address them. Not having full access to Linux isn't a big deal, until it is, and I'm pretty sure that if you could install and run the actual zap2xml program rather than that adaptation you would not be having this issue, because I know of two different systems running zap2xml under Ubuntu server and neither are experiencing this.
I wish I could help you, if only because I'm kind of p.o.'ed about the other reply you got, and if I could I would fix your issue myself. But unfortunately you have locked yourself into an ecosystem that very much does things in non-standard ways, and while I realize that a lot of people use those distros, the sad truth is that when things stop working right you pretty much have to deal with the creators of those distros (and the addon authors), because nobody who doesn't use their software knows what they've done, and what they've changed from the original programs. In the case of zap2xml specifically, the original program was written in Perl but in the dim recesses of my memory I recall that whoever created that addon converted it to Python (or some language other than the original), so even the original zap2xml author probably wouldn't recognize the code.