4suite server fails to start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-4suite (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: python-4suite
I tried installing 4suite tonight and I found that it did not want to start. Several issues arose.
1) The init script has bashism that cause it to fail. Replacing /bin/sh with /bin/bash gets it to work. The specific bashism seems to be the use of local.
2) The shell variables PIDDIR and LOGDIR are not defined and as such it can't create those directories and chown them. They should be /var/{run,
3) The way that the config file seems to suggest to give the init script the username and password don't seem to work. As such 4ssd seems to just sit there and then times out. I'm not sure how to fix this. Though running the 4ss_manager by hand and inputing the username and password you selected while initing seems to work out well.
4) The docs are kinda vague on the need for the user to run init. Its in the doc package, but I would expect such a necessary action to be in the README.Debian.
I believe that that is it. I know I'm reporting 5 separate bugs in the same bug report, but they are all related and any one will stop anyone from even trying 4suite cause its so hard to get up and running.
Ditto #1 and #2.
5) /var/lib/4Suite was root:root instead of ftss:ftss, as documentation said it would be -- so running 4ss_manager (as docs recommended) wouldn't work after a fresh install.
For context though, and I'm not reporting this as a bug since it may be my own fault: 4ssd seems to start up fine (su ftss -c "4ss_manager start"), no complaints in the log file, but doesn't listen on a port (according to "4ss_manager status" and "nmap localhost") -- so I've got no way to communicate with it except through `kill`.