Project

General

Profile

Bug #414

Ajaxterm does not start at run level 3

Added by prickly almost 11 years ago. Updated almost 10 years ago.

Status:
Assigned
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
01/17/2010
Due date:
% Done:

0%


Description

Ajaxterm has started to not work now that I have switched to run level 3.

I can uninstall it and then reinstall to get it working again, but when I reboot it "breaks" again and I get a 503 Service is Temporarily Unavailble error.

History

#1 Updated by cpg almost 11 years ago

  • Status changed from New to Assigned
  • Assignee set to cpg

I think this should work to restart it every time the machine boots.

Add this line to the file /etc/rc.local:

(cd /var/hda/web-apps/ajaxterm/html/ && ./ajaxterm.py -d)

please do report back here how it works.

#2 Updated by prickly almost 11 years ago

cpg wrote:

I think this should work to restart it every time the machine boots.

Add this line to the file /etc/rc.local:

(cd /var/hda/web-apps/ajaxterm/html/ && ./ajaxterm.py -d)

please do report back here how it works.

Thanks for looking in to this.

I think that I am partially able to confirm that this works as I do not get the " 503 Service is Temporarily Unavailble" error anymore. But I must be having other issues all of a sudden as ajaxterm and dokuwiki are both no longer available - "Internet Explorer cannot display the webpage" (I do not think that this is related to this issue though).

#3 Updated by bigfoot65 almost 10 years ago

Updated the install/uninstall script to use apache crontab with @reboot. The service starts on reboot now. The kill process command for uninstall also works. Recommend this bug be closed.

Also available in: Atom