Re: JAXL keeps dying

[Abhinav Singh]

1) have you enabled xep-0199 (xmpp ping)?

2) run your bot with log level set to JAXL_DEBUG and you will get some hint from log file at the time of disconnections

    (if you get some, paste them here, we can possibly help further)

--

Abhinav

On Friday, November 23, 2012 11:24:44 PM UTC+5:30, JD wrote:

Noob Disclaimer.

I am using a mildly modified echobot for sending pre-programmed responses through gtalk. Problem is, the JAXL process keeps getting terminated every few hours (or sooner).

How to:

1) Know why this keeps happening?

2) Restart JAXL automatically if it dies?

Appreciate your help

J

[JD]

Sorry for the late reply. What is the path to the log file to look at?

Another question:

How can I use JAXL to send out fixed messages on a schedule? Right now I have a cronjob that invokes JAXL (v2.0) to accomplish this. With JAXL3.0 running as a continuous process, can I somehow access the process to trigger messages from another file? Any sample code would be helpful!

Thanks,

JD

[Murali Krishna P]

There are periodic clock and you can also set the time..

see the jaxl documentation

--
Documentation: http://jaxl.readthedocs.org/en/latest/index.html
Create a bug/issue: https://github.com/abhinavsingh/JAXL/issues/new
 
You received this message because you are subscribed to the Google Groups jaxl group. To post to this group, send email to ja...@googlegroups.com. To unsubscribe from this group, send email to jaxl+uns...@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/jaxl?hl=en-US
 
 

--

- Thanks & Regards

 Murali Krishna

Computer Science  Engineer

Hyderabad-70

pmuralik...@gmail.com 

[Abhinav Singh]

Jaxl by default will log everything to console.

However, you can specify a constructor config called 'log_path' to redirect everything into a file.

Read constructor options documentation for more detail.

For scheduling stuff, kindly read cron jobs documentation.

It provides all that you will ever need. And please, using v2.x with v3.x isn't really a wise choice.

Unexpected behaviour should be expected, until you know whats really going on.

--

Abhinav

[乐管]

I'm having the same problem. I use Jaxl v3 to connect to ejabberd. The system is Unbuntu 10.

Jaxl works well for 2-3 hours after connection. But suddenly aborted. Log shows few info:

jaxl:222 - 2013-08-07 16:39:51 - strict mode enabled, adding exception handlers. Set 'strict'=>TRUE inside JAXL config to disable this

jaxl:167 - 2013-08-07 16:39:51 - created pid file /opt/dev/myip/SER/JAXL/.jaxl/run/jaxl_16206.pid

jaxl:180 - 2013-08-07 16:39:51 - dns srv lookup for myip

jaxl_socket_client:95 - 2013-08-07 16:39:51 - trying tcp://myip

jaxl:214 - 2013-08-07 19:58:44 - cleaning up pid and unix sock files

jaxl_clock:55 - 2013-08-07 19:58:44 - shutting down clock server...

I've enabled xmpp ping. But after checking ejabberd log, it shows not supported by default. So I disabled xmpp ping----but nothing changed.

Any suggestion will be helpful!