XMPP Plus

Questions and comments specific to a particular plugin should go here.
Post Reply
Snowbird
Experienced User
Posts: 374
Joined: Fri Jul 03, 2009 10:04 am

Re: XMPP Plus

Post by Snowbird » Sun May 20, 2018 6:12 am

thx, i'm going to try it now :)
Top
HTPCanwender
Experienced User
Posts: 89
Joined: Wed Feb 08, 2012 9:41 pm
Location: Germany

Re: XMPP Plus

Post by HTPCanwender » Mon May 21, 2018 5:57 am

Hi,
the plugin worked for 15 hours. Now its offline. I will start eventghost again.

14:35:56 XMPPPlus.jabber.de:5222.Connected
14:35:59 XMPPPlus.xxxxxxxx@jabber.de.AuthenticationSuccessful
14:36:00 XMPPPlus.xxxxxxxx@jabber.de.SessionStarted
.
..
06:01:37 XMPPPlus.jabber.de:5222.SocketError
06:01:37 XMPPPlus.xxxxxxxx@jabber.de.SessionEnded
06:01:37 XMPPPlus.jabber.de:5222.SocketError
06:01:37 XMPPPlus.xxxxxxxx@jabber.de.SessionEnded
06:01:38 XMPPPlus.jabber.de:5222.SocketError

Yours.
Arnd
Top
User avatar
kgschlosser
Site Admin
Posts: 5508
Joined: Fri Jun 05, 2015 5:43 am
Location: Rocky Mountains, Colorado USA

Re: XMPP Plus

Post by kgschlosser » Mon May 21, 2018 7:55 am

Even if it is offline it should continue to keep on trying to reconnect. The socket error i believe is because it i unable to connect to the server.

I can see if maybe i can add the actual socket error to the event so maybe we can get more detail as to what is going on.
If you like the work I have been doing then feel free to Image
Top
Snowbird
Experienced User
Posts: 374
Joined: Fri Jul 03, 2009 10:04 am

Re: XMPP Plus

Post by Snowbird » Mon May 21, 2018 8:15 am

kgschlosser wrote: ↑
Mon May 21, 2018 7:55 am
 Even if it is offline it should continue to keep on trying to reconnect. The socket error i believe is because it i unable to connect to the server.
Honestly, I'm pretty sure it's not what it's happening, what I think is that the connection gets lost for some reason (internet problem or the server is having difficulties, etc.) then EG loses the connection and isn't able to reestablish the connection on its own. Why I think this ? because when it stops working, all I need to do is to close/launch EG and it works right away. So either the "keep try to reconnect" function is not working, or the the detection of a server failure is not properly detected, hence it's not even trying to reconnect.

kgschlosser wrote: ↑
Mon May 21, 2018 7:55 am
 I can see if maybe i can add the actual socket error to the event so maybe we can get more detail as to what is going on.
It wouldn't hurt, and will probably gives us some useful information.
Top
HTPCanwender
Experienced User
Posts: 89
Joined: Wed Feb 08, 2012 9:41 pm
Location: Germany

Re: XMPP Plus

Post by HTPCanwender » Mon May 21, 2018 7:45 pm

The second try gave the same result:

07:59:03 XMPPPlus.jabber.de:5222.Connected
07:59:04 XMPPPlus.xxxxxxxx@jabber.de.AuthenticationSuccessful
07:59:05 XMPPPlus.xxxxxxxx@jabber.de.SessionStarted
.
.
13:29:30 XMPPPlus.jabber.de:5222.SocketError
13:29:30 XMPPPlus.xxxxxxxx@jabber.de.SessionEnded
13:29:30 XMPPPlus.jabber.de:5222.SocketError
13:29:30 XMPPPlus.xxxxxxxx@jabber.de.SessionEnded
13:29:31 XMPPPlus.jabber.de:5222.SocketError
Top
User avatar
kgschlosser
Site Admin
Posts: 5508
Joined: Fri Jun 05, 2015 5:43 am
Location: Rocky Mountains, Colorado USA

Re: XMPP Plus

Post by kgschlosser » Mon May 21, 2018 10:33 pm

as I has stated before. i removed the timeout period on the reconnects. So it should keep on trying to connect it will try to reconnect on a socket error every 10 seconds. the only thing i am seeing are 2 attempts to reconnect.

Is it continuing to loop and you are not posting that log information?

and I will see what i can do about getting the actual socket error.
If you like the work I have been doing then feel free to Image
Top
HTPCanwender
Experienced User
Posts: 89
Joined: Wed Feb 08, 2012 9:41 pm
Location: Germany

Re: XMPP Plus

Post by HTPCanwender » Tue May 22, 2018 11:30 am

I postet all socket errors. There are no additional ones.
Top
User avatar
kgschlosser
Site Admin
Posts: 5508
Joined: Fri Jun 05, 2015 5:43 am
Location: Rocky Mountains, Colorado USA

Re: XMPP Plus

Post by kgschlosser » Tue May 22, 2018 3:41 pm

what are the entries with the dots? there is no date stamp for those.
If you like the work I have been doing then feel free to Image
Top
User avatar
kgschlosser
Site Admin
Posts: 5508
Joined: Fri Jun 05, 2015 5:43 am
Location: Rocky Mountains, Colorado USA

Re: XMPP Plus

Post by kgschlosser » Tue May 22, 2018 3:48 pm

Snowbird wrote: ↑
Mon May 21, 2018 8:15 am
 the the detection of a server failure is not properly detected, hence it's not even trying to reconnect.
It is detecting the disconnect. hence the multiple socket errors. those only occur when a reconnect attempt is made. This is why i do not understand as to how the problem is with EG. because if the socket bombs and a new connection is attempted the new connection is made on a new outgoing port to the server. for some reason something is stopping that from happening. firewall? router? IDK. I have been testing the snot out of this and it reconnects every time. I have an XMPP server set up that i have EG connect to. then i end the task for the server. EG gets the expected sockets errors. as soon as i start the service back up it connects and all is good.

I am not stating the problem does not exist. I am trying to figure out what the hell could be causing it. I am going to have to go and mess with the library that i am using to get better logging output. I have tried it without getting into that end of it because the author's code has a lot of voodoo in it.
If you like the work I have been doing then feel free to Image
Top
Snowbird
Experienced User
Posts: 374
Joined: Fri Jul 03, 2009 10:04 am

Re: XMPP Plus

Post by Snowbird » Tue May 22, 2018 3:50 pm

kgschlosser wrote: ↑
Tue May 22, 2018 3:41 pm
 what are the entries with the dots? there is no date stamp for those.
I think the dots are simply there to simulate all other events/actions not related and not useful for this matter. There's no need to display them :)
He will confirm this (or not), that's only my guess :)
Top
Snowbird
Experienced User
Posts: 374
Joined: Fri Jul 03, 2009 10:04 am

Re: XMPP Plus

Post by Snowbird » Tue May 22, 2018 4:08 pm

kgschlosser wrote: ↑
Tue May 22, 2018 3:48 pm
Snowbird wrote: ↑
Mon May 21, 2018 8:15 am
 the the detection of a server failure is not properly detected, hence it's not even trying to reconnect.
It is detecting the disconnect. hence the multiple socket errors. those only occur when a reconnect attempt is made. This is why i do not understand as to how the problem is with EG. because if the socket bombs and a new connection is attempted the new connection is made on a new outgoing port to the server. for some reason something is stopping that from happening. firewall? router? IDK. I have been testing the snot out of this and it reconnects every time. I have an XMPP server set up that i have EG connect to. then i end the task for the server. EG gets the expected sockets errors. as soon as i start the service back up it connects and all is good.

I am not stating the problem does not exist. I am trying to figure out what the hell could be causing it. I am going to have to go and mess with the library that i am using to get better logging output. I have tried it without getting into that end of it because the author's code has a lot of voodoo in it.
Kevin, I know you have tested all this thoroughly, and you need more clues to fix this, but I gave you all I have, I tried many things to understand why this is happening and couldn't understand either, it simply doesn't make sense... Why in the world it works 3 or 4 days in a row, and suddenly stops working ? sometimes it disconnects twice a day with no obvious reason, and sometimes it just works for days... There is one thing that i'm sure of, when the problem occurs, all I need to do is to shut down EG and run it again, and it connects immediately, so EG should be included in the equation ! Could it be some TCP connection that gets stuck on the server side, and when EG tries to reconnect, the server refuses it because it thinks it's already connected because there is still an ongoing connection between them ? maybe a socket that didn't close properly on one end, but as far as I know there is a mechanism for that to "free" the socket when the connection is gone (some sort of TimeOut). I don't know what's going on, but the problem exists.

That being said, since I installed your latest version of the plugin, I didn't have any problem, but that doesn't mean the problem is solved, it could take days to occur. On the other hand, HTPCanwender is still getting the disconnection issue, so... that makes me think that the problem is still there, even if for me all is fine for now.
Top
User avatar
kgschlosser
Site Admin
Posts: 5508
Joined: Fri Jun 05, 2015 5:43 am
Location: Rocky Mountains, Colorado USA

Re: XMPP Plus

Post by kgschlosser » Tue May 22, 2018 5:39 pm

HMMMMM that makes me think... Maybe... the library does not close the connection properly and what is happening is you do not get logged off from the Server. and because you are not logged off it is not allowing another connection. But one would think thins would not cause a socket error. it would be a authentication error.

I have a sneaky suspicion that when i close the client it doesn't get deleted and when we create a new one it simply uses the already made one the library has cached. I can clear the modules from python and reload it and then create the client again. see if possibly that clears it up.
If you like the work I have been doing then feel free to Image
Top
User avatar
kgschlosser
Site Admin
Posts: 5508
Joined: Fri Jun 05, 2015 5:43 am
Location: Rocky Mountains, Colorado USA

Re: XMPP Plus

Post by kgschlosser » Tue May 22, 2018 5:43 pm

also how sockets work is when a server listens on a port it is able to have multiple connections to that port. then a client initializes a connection to the server an outgoing port on the client machine is chosen at random. it is not supposed to try and use the same one. so even if the client port is stuck it shouldn't matter because it is going to randomly pick a new one. and since the server has the ability to handle multiple connections there shouldn't be an issue there either. The only case where this does not hold true is if for some reason on the client side the coder decided to use the same outgoing port over and over again. This is where i believe that caching thing might be the culprit.
If you like the work I have been doing then feel free to Image
Top
HTPCanwender
Experienced User
Posts: 89
Joined: Wed Feb 08, 2012 9:41 pm
Location: Germany

Re: XMPP Plus

Post by HTPCanwender » Tue May 22, 2018 8:21 pm

I have nothing new to report. Even the third try stoped with the same messages.
Here are all messages XMPPplus made during the session.

21:48:10 ---> Willkommen beim EventGhost <---
21:48:13 Autostart

21:48:13 XMPPPlus.jabber.de:5222.Connected

21:48:17 XMPPPlus.boekifhz@jabber.de.AuthenticationSuccessful
21:48:17 XMPPPlus.boekifhz@jabber.de.SessionStarted

21:48:17 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077FBA70>
21:48:17 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2BF0>
21:48:17 XMPPPlus.boekifhz@jabber.de.RosterReceived

21:52:54 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x06B68EB0>
21:52:57 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2BF0>
21:53:26 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A6230>
21:53:26 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0780A770>
21:53:27 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077FB330>

22:09:30 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2C70>

22:24:01 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077FB330>
22:24:17 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779D6F0>
22:24:17 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2F90>
22:24:18 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x078403B0>
22:24:54 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2870>
22:24:54 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A6C30>
22:24:55 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2570>
22:27:16 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077FB090>
22:27:17 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A6B90>
22:27:51 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779DAF0>
22:27:51 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x078403B0>
22:27:51 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A6ED0>

23:54:31 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779DAF0>
23:54:32 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827CB0>
02:34:02 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x078270F0>
02:34:03 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077FB5F0>

05:33:43 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A66F0>

05:39:11 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827E70>
05:39:13 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2190>
05:39:48 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A6AF0>
05:39:48 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07840130>
05:45:27 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2C70>
05:45:28 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x06B68EF0>
05:52:09 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x078403B0>
05:52:10 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x06B68EF0>
05:57:18 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2C70>
06:11:40 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2A90>
06:31:55 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077F6270>
06:33:13 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2A10>
06:33:13 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A63B0>
06:33:14 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077F63D0>
06:39:21 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A24F0>
06:39:23 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827E70>
06:47:30 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077F6270>
06:47:31 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2570>
06:48:07 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827B50>
06:48:07 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779D870>
06:48:07 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779DBF0>
07:07:29 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779D250>
07:08:22 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779D630>
07:09:07 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2A10>
07:09:07 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A6ED0>
07:09:07 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2A10>
07:09:08 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07801910>
07:14:38 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077F63D0>
07:14:38 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07801910>
07:20:07 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779D270>
07:20:08 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07801910>
07:25:38 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779D270>
07:25:38 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2C90>
07:29:18 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779DBF0>
07:29:20 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A63B0>
07:46:48 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779DA70>
08:02:02 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779D870>
08:15:01 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077F6790>
08:31:00 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827B50>
08:45:55 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077F6250>
08:45:56 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2AF0>
08:48:46 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779DA70>
08:48:46 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A65B0>
08:48:47 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077F6790>
08:50:37 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779D270>
08:50:38 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A65B0>
09:27:56 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2310>
09:37:33 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A63B0>
09:37:34 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827E50>
09:42:05 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077F6250>
09:42:05 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2F90>
09:43:19 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2D30>
09:48:48 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827E70>
09:48:49 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077FB5F0>
10:05:47 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2D30>
10:05:48 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827B50>
10:06:22 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077FB330>
10:06:23 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A6C30>
10:06:33 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077FB670>
10:23:16 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2090>
10:23:17 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2870>
10:23:46 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2D30>
10:23:46 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0780A770>
10:23:46 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2D30>
10:43:26 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A6C30>
10:59:02 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x078016B0>
11:01:28 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827310>
11:29:55 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827CB0>
11:29:57 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779D370>
11:30:27 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077FB3D0>
11:30:29 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827E50>
11:32:30 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779D370>
11:37:56 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x078016B0>
11:54:24 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0780A770>
11:54:25 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0780A1F0>
12:05:02 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827BB0>
12:05:41 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827BD0>
12:07:15 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779D630>
12:07:16 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827BD0>
12:08:02 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A66F0>
12:08:02 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2D30>
12:08:02 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2570>
12:15:51 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A6230>
12:15:51 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A63B0>
12:16:45 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779DAF0>
12:16:45 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2BF0>
12:16:46 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A6ED0>
12:22:15 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A6AF0>
12:22:17 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779D9B0>
12:32:54 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827B50>

12:47:43 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07801890>
12:49:38 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779D370>
12:49:39 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A6FF0>
12:55:10 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779DE70>
12:55:11 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x0779DCD0>

13:02:38 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077A2910>

13:55:52 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x07827CB0>
14:01:56 XMPPPlus.boekifhz@jabber.de.Incoming.Presence <eg.CorePluginModule.XMPPPlus.Presence object at 0x077FB670>
14:08:51 XMPPPlus.jabber.de:5222.SocketError
14:08:51 XMPPPlus.boekifhz@jabber.de.SessionEnded
14:08:51 XMPPPlus.jabber.de:5222.SocketError
14:08:51 XMPPPlus.boekifhz@jabber.de.SessionEnded
14:08:51 XMPPPlus.jabber.de:5222.SocketError
Top
HTPCanwender
Experienced User
Posts: 89
Joined: Wed Feb 08, 2012 9:41 pm
Location: Germany

Re: XMPP Plus

Post by HTPCanwender » Wed May 23, 2018 5:21 am

Could you please insert an event that schows the version number of the plugin when it starts? I want to check if the installation routine worked correct and if i am using the newest version.
Top
Post Reply

Return to “Plugin Support”