serge Posted April 28, 2015 Report Share Posted April 28, 2015 I upgraded to debian 8 one of my server, and only issue were 5 services like ssh, php5-fpm, mysql, nginx, etc was not started after reboot, but I was only able to start them manually like this "systemctl start MY-SERVICE" and because now debian come by default with systemd, it's mean you need to enable service you want that start at boot, doing this command line way: systemctl enable MY-SERVICE but in my case even by doing this above did not do the trick, so I went back to sysv following this instruction: http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_a_Debian_jessie/sid_installation As after that & reboot server, my services still not started, so doing this done the trick at my next reboot: sysv-rc-conf --level 345 SERVICE-NAME on Quote Link to comment Share on other sites More sharing options...
Paul Posted April 28, 2015 Report Share Posted April 28, 2015 I didn't realize debian was moving over to systemd also. I'm just getting use to it on CentOS 7. Quote Link to comment Share on other sites More sharing options...
Michael Posted April 28, 2015 Report Share Posted April 28, 2015 Ah I thought Debian 7 is what Centos 7 used Quote Link to comment Share on other sites More sharing options...
serge Posted April 28, 2015 Author Report Share Posted April 28, 2015 It's seem debian 8 (Jessie) adoption to systemd was very controvertial as no choise to keep sysv was proposed during updrade process when some users can have very custom config they will preffer to keep. From my personal experience systemd is certainly good but impose such switching is certainly not good, I believe debian will lose a lot of people with that. Quote Link to comment Share on other sites More sharing options...
cloudrck Posted September 3, 2015 Report Share Posted September 3, 2015 It's seem debian 8 (Jessie) adoption to systemd was very controvertial as no choise to keep sysv was proposed during updrade process when some users can have very custom config they will preffer to keep. From my personal experience systemd is certainly good but impose such switching is certainly not good, I believe debian will lose a lot of people with that. I disagree, systemd is a drop-in replacement for SysV. You can use your SysV scripts with systemd as long as they don't declare incomplete dependencies in your LSB block. You can't please everyone, people complain when you stay the same and don't innovate, people complain when you change. Damned if you do, damned if you don't. I happen to like the clean syntax for systemd much more than SysV. Michael 1 Quote Link to comment Share on other sites More sharing options...
Paul Posted September 3, 2015 Report Share Posted September 3, 2015 I am starting to like systemd and getting use to running systemctl, it's logical. I just have many many years doing it the old way so that's what wants to flow out of my finger tips. Michael 1 Quote Link to comment Share on other sites More sharing options...
serge Posted September 4, 2015 Author Report Share Posted September 4, 2015 By the way, since the upgrade of distro version the considered server I was saying at starting this post, is not able after a reboot to start basic service like ssh, mysql, nginx, ect... And since the upgrade, nevermind using systemd or back to sysv, as most of my services can now just only start manually, so I preffer to be "dammed" to say I had preffer do have the choice of not runnning such issue by keep sysv in the upgrade process. Quote Link to comment Share on other sites More sharing options...
serge Posted September 8, 2015 Author Report Share Posted September 8, 2015 I solved my issue, by the way, since OS upgrade, server switched in maintenance mode (single-user-mode) at boot, but I did not figured before, so I corrected Paul 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.