0
Not a bug

Ajenti didn't restart after 1.2.7 update..

Andre Greeff 7 years ago updated by Eugene Pankov (Project coordinator) 7 years ago 1

Calling this a 'bug' seems overkill, it's really just a quick note.. Running `service ajenti start` in terminal (Ubuntu Server 12.10) started it up again without any errors, but it didn't restart on it's own.

Answer

Answer
Not a bug

Sorry about that, but we can't reliably restart it with Debian packaging system.

Why is that so? Because the package post-installation script is being run before python-support triggers are run. And before they are run, the application's python files may not yet be placed in the python dist-packages dir :(

GOOD, I'M SATISFIED

It's really not a problem.. I think for most people working on Linux, doing stuff manually is sort of second nature, all these automated systems are simply "nice to have". Wasn't sure if this was a known issue or not though, so I wanted to leave a message just in case. :)


Just a thought, but if you can detect the OS, perhaps you could include a message in the update screen to mention this little quirk (thinking more for the people who wouldn't normally know how to start it up again manually).

Satisfaction mark by Andre Greeff 7 years ago
Answer
Not a bug

Sorry about that, but we can't reliably restart it with Debian packaging system.

Why is that so? Because the package post-installation script is being run before python-support triggers are run. And before they are run, the application's python files may not yet be placed in the python dist-packages dir :(

+1

Actually there's the message after the installation:

"Now start Ajenti with 'service ajenti restart'" :)