ajaxterm does not work in daemon mode

Bug #397951 reported by Nikolaus Rath on 2009-07-10
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
ajaxterm (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: ajaxterm

When started with --daemon (as done in the init.d script), ajaxterm only serves the very first page on my system. Immediately afterwards, I get 'Connection error status:502' in the first line right after 'Get'. When started without --daemon, everything works fine. Unfortunately ajaxterm doesn't seem to do any logging when started in daemon mode, so there are no error messages.

Régis Dupuy (regis-dupuy) wrote :

exactly the same for me.

Malte S. Stretz (mss) on 2010-05-25
summary: - Does not work in daemon mode
+ ajaxterm does not work in daemon mode
Julien Valroff (julienv) wrote :

Hi,

What is the contents of /etc/default/ajaxterm?

what happens if you start ajaxterm with --daemon as root in a console?

Cheers,
Julien

Malte S. Stretz (mss) wrote :

In /etc/default/ajaxterm everything is commented out. ajaxterm is started as
  python /usr/share/ajaxterm/ajaxterm.py --daemon --port=8022 --serverport=22 --uid=ajaxterm

Running this in a root shell just gives
  AjaxTerm at http://localhost:8022/ pid: 4604

As Nikolaus wrote, without --daemon it works fine.

Julien Valroff (julienv) wrote :

Hi,

When starting as root in a shell, can you connect to ajaxterm on port 8022?

Cheers,
Julien

Malte S. Stretz (mss) wrote :

From the initial comment: "When started with --daemon (as done in the init.d script), ajaxterm only serves the very first page on my system. Immediately afterwards, I get 'Connection error status:502' in the first line right after 'Get'."

rkantos (robin-karinen) wrote :

Same prob here, working fine without daemon. On Ubuntu 10.04

Julien Valroff (julienv) wrote :

Hi,

Which is your default python version?
% python -V

Cheers,
Julien

Malte S. Stretz (mss) wrote :

Python 2.6.4

Chuck Short (zulcss) on 2011-06-09
Changed in ajaxterm (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Julien Valroff (julienv) wrote :

Hi,

Following to a similar bug reported on Debian, we have found that this kind of bug was caused by using a non UTF-8 locale, or similarly, when using non UTF-8 encoded filenames.

See: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608340

Cheers,
Julien

Dave Hamer (ncxb) wrote :

Is there a work around for this that still allows you to use Daemon mode?

my locale was previously set to "LANG=" - however I've now updated it to UTF8...

Thanks; Dave

Currently running: Ubuntu 10.10

New locale output:
locale
LANG=en_GB.UTF-8
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.