Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
On Thursday, August 14, 2014 10:10:02 PM UTC+5:30, Michael Biebl wrote: Am 14.08.2014 16:02, schrieb Rusi Mody: On Thursday, August 14, 2014 3:40:03 PM UTC+5:30, Michael Biebl wrote: Am 14.08.2014 um 05:32 schrieb Rusi Mody: Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /dev/ppp device: No such file or directory Since you don't have the /dev/ppp device, I assume you are not using udev 208-7? Could you please post the version of udev (and systemd) you are using? Thanks Michael Just ran an aptitude update. After that: udev is at 208-6 which is the latest I see If you are using sysvinit as PID 1, upgrade udev to 208-7 (currently available from unstable) systemd is at 204-8 upgradable to 208-6 If you are using systemd as PID 1, you should avoid mixing udev 208 with systemd 204 and always upgrade both [1]. I'd suggest you install systemd-sysv (which will uninstall sysvinit-core) which will switch your default init to systemd. You will still have a fallback /lib/sysvini/init as long as the sysvinit package is installed and which you can use to boot the system in case the boot fails with systemd. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=75#35 Done finally! sysvinit-core removed which pulled in systemd-sysv and (to the best of my knowledge!) my system is still running! So Thanks again! [I would still like to very most humbly submit that sysvinit-core is an odd name for something that is not core! At the least the description lines could have something to that effect...] -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/03c6e184-4da2-4d51-b64f-91c95b6f7...@googlegroups.com
Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
On Tue, 19 Aug 2014, Chris Bannister wrote: On Mon, Aug 18, 2014 at 05:38:13AM -0700, Rusi Mody wrote: More specifically my concerns are: 1. Which apt package 'owns' which file? Use 'dpkg -S' e.g.: And if you need to do this often, I recommend the dlocate package. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140819110306.gb3...@khazad-dum.debian.net
Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
On Thursday, August 14, 2014 10:10:02 PM UTC+5:30, Michael Biebl wrote: Am 14.08.2014 16:02, schrieb Rusi Mody: On Thursday, August 14, 2014 3:40:03 PM UTC+5:30, Michael Biebl wrote: Am 14.08.2014 um 05:32 schrieb Rusi Mody: Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /dev/ppp device: No such file or directory Since you don't have the /dev/ppp device, I assume you are not using udev 208-7? Could you please post the version of udev (and systemd) you are using? Thanks Michael Just ran an aptitude update. After that: udev is at 208-6 which is the latest I see If you are using sysvinit as PID 1, upgrade udev to 208-7 (currently available from unstable) systemd is at 204-8 upgradable to 208-6 If you are using systemd as PID 1, you should avoid mixing udev 208 with systemd 204 and always upgrade both [1]. I'd suggest you install systemd-sysv (which will uninstall sysvinit-core) which will switch your default init to systemd. You will still have a fallback /lib/sysvini/init as long as the sysvinit package is installed and which you can use to boot the system in case the boot fails with systemd. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=75#35 Just trying to complete this (both in deed and in understanding) And I find that /bin/systemd is a link to /lib/systemd/systemd. This removes some of my apprehensions. [I could have sworn that I saw a normal file of same size in both places and was confused. I guess I saw wrong.] And now (IIUC) replacing sysvinit-core by systemd-sysv will make systemd the default (right now Ive to explicitly give the init=/bin/systemd at grub). However both will continue to exist and in case of any issue it could be manually chosen. Is that right?? More specifically my concerns are: 1. Which apt package 'owns' which file? 2. Are any critical packages being obsoleted? I really wonder about the name 'sysvinit-core'... Hardly seems 'core' to me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/6cc11efb-03b8-462d-b1f6-3bd7f1b57...@googlegroups.com
Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
On Mon, Aug 18, 2014 at 05:38:13AM -0700, Rusi Mody wrote: More specifically my concerns are: 1. Which apt package 'owns' which file? Use 'dpkg -S' e.g.: root@tal:~# dpkg -S /bin/systemd systemd: /bin/systemd root@tal:~# dpkg -S /lib/systemd/systemd systemd: /lib/systemd/systemd -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140819031813.GA28646@tal
Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
On Thu, Aug 14, 2014 at 12:14 PM, Rusi Mody rustompm...@gmail.com wrote:
On Thursday, August 14, 2014 9:10:02 PM UTC+5:30, Tom H wrote:
On Thu, Aug 14, 2014 at 10:32 AM, Rusi Mody wrote:
To add to my earlier report:
I managed to remove graphviz and its associated libraries.
So that now aptitude dist-upgrade gives me only 1 'issue' :
The following packages have unmet dependencies:
systemd-sysv : Conflicts: sysvinit-core but 2.88dsf-53.3 is to be installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) sysvinit-core
You can either accept to remove sysvinit-core and run with systemd
only or install systemd-shim and you won't be prompted to install
systemd-sysv - and you'll be able to boot with sysvinit by default or
systemd if you add init=/lib/systemd/systemd to the kernel cmdline.
(the archives have this repeated a number of times!)
systemd-shim is currently installed
OK, although it doesn't make sense. systemd-sysv shouldn't be pulled in.
This is on an unstable system:
# dpkg-query -W -f='${Package}\n${Version}\n${Status}\n\n'
{init,systemd,systemd-shim,systemd-sysv,sysvinit,sysvinit-core,udev}
init
1.20
install ok installed
systemd
208-7
install ok installed
systemd-shim
6-5
install ok installed
systemd-sysv
unknown ok not-installed
sysvinit
2.88dsf-55.2
install ok installed
sysvinit-core
2.88dsf-53.3
install ok installed
udev
208-7
install ok installed
# aptitude search -F%p '?depends(systemd-sysv)'
gpsd
init
libpam-systemd
sysvinit
# aptitude search -F%p '?depends(systemd-shim)'
libpam-systemd
# aptitude search -F%p '?depends(sysvinit-core)'
init
sysvinit
# apt-cache show gpsd | grep Depends
Depends: netbase | systemd-sysv, ...
# dpkg -L netbase
/.
/etc
/etc/rpc
/etc/protocols
/etc/services
/etc/network
/usr
/usr/share
/usr/share/doc
/usr/share/doc/netbase
/usr/share/doc/netbase/copyright
/usr/share/doc/netbase/changelog.gz
# apt-cache show netbase | grep Priority
Priority: important
Given the Priority of netbase, neither gpsd nor the other three
should be pulling in systemd-sysv unless you don't have sysvinit-core
or systemd-shim installed - although the netbase | systemd-sysv is
weird.
Running with init=/bin/systemd makes networking stop working
IIRC, it's a question of moving the module options from /etc/modules
to /etc/modprobe.d/module.conf until the systemd maintainers
figure out how to do this on transition to systemd.
And /bin/systemd is softlinked to /lib/systemd/systemd so I guess that
is a non-difference
/bin/systemd is a Debianism but as you say it doesn't make a difference.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/CAOdo=SwdofZyF5Jb4gJzQgueLkoCxyZR6Y+Lw8v4kK=gahs...@mail.gmail.com
Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
Am 14.08.2014 um 05:32 schrieb Rusi Mody: Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /dev/ppp device: No such file or directory Since you don't have the /dev/ppp device, I assume you are not using udev 208-7? Could you please post the version of udev (and systemd) you are using? Thanks -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
On Thursday, August 14, 2014 3:40:03 PM UTC+5:30, Michael Biebl wrote: Am 14.08.2014 um 05:32 schrieb Rusi Mody: Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /dev/ppp device: No such file or directory Since you don't have the /dev/ppp device, I assume you are not using udev 208-7? Could you please post the version of udev (and systemd) you are using? Thanks Michael Just ran an aptitude update. After that: udev is at 208-6 which is the latest I see systemd is at 204-8 upgradable to 208-6 Trying to upgrade systemd gives me: colord will be removed gnome-sushi will be removed gvfs will be removed gvfs-backends will be removed gvfs-daemons will be removed libpam-systemd will be removed nautilus will be removed packagekit will be removed packagekit-tools will be removed policykit-1 will be removed policykit-1-gnome will be removed udisks2 will be removed libsystemd-daemon0 (version 204-8) will be upgraded to version 208-6 libsystemd-journal0 (version 204-8) will be upgraded to version 208-6 libsystemd-journal0:i386 (version 204-8) will be upgraded to version 208-6 libsystemd-login0 (version 204-8) will be upgraded to version 208-6 nautilus-data (version 3.8.2-3) will be upgraded to version 3.12.2-1 systemd (version 204-8) will be upgraded to version 208-6 Some other things which I looked at: Trying to upgrade libpam-systemd gives me sysvinit-core will be removed libpam-systemd (version 204-8) will be upgraded to version 208-6 libsystemd-daemon0 (version 204-8) will be upgraded to version 208-6 libsystemd-journal0 (version 204-8) will be upgraded to version 208-6 libsystemd-journal0:i386 (version 204-8) will be upgraded to version 208-6 libsystemd-login0 (version 204-8) will be upgraded to version 208-6 systemd (version 204-8) will be upgraded to version 208-6 systemd-sysv (version 208-6) will be installed sysvinit is at 2.88dsf-53.2 upgradable to 2.88dsf-53.3 Trying to upgrade sysvinit gives: sysvinit (version 2.88dsf-53.2) will be upgraded to version 2.88dsf-53.3 init (version 1.20) will be installed which seems the least drastic so far! I find that on trying aptitude dist-upgrade I get a large load of installs/upgrades and these removes: Remove the following packages: 1) graphviz 2) rsyslog 3) sysvinit-core Keep the following packages at their current version: 4) libgvc6 [Not Installed] 5) liblognorm1 [Not Installed] So I try to remove graphviz and related libs but I get E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. E: Unable to correct dependencies E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. E: Unable to correct dependencies E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. E: Unable to correct dependencies E: Unable to lock the download directory So I am going to try to remove graphviz and its libraries one piece at a time... Meanwhile if you have any further advice... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/ed2f8f3e-5d91-4524-a2be-1e70a8028...@googlegroups.com
Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
On Thursday, August 14, 2014 8:00:03 PM UTC+5:30, Rusi Mody wrote: On Thursday, August 14, 2014 3:40:03 PM UTC+5:30, Michael Biebl wrote: Could you please post the version of udev (and systemd) you are using? Thanks Michael To add to my earlier report: I managed to remove graphviz and its associated libraries. So that now aptitude dist-upgrade gives me only 1 'issue' : The following packages have unmet dependencies: systemd-sysv : Conflicts: sysvinit-core but 2.88dsf-53.3 is to be installed. The following actions will resolve these dependencies: Remove the following packages: 1) sysvinit-core -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/f5ced6dd-b9af-4095-8bd9-34177ce73...@googlegroups.com
Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
On Thu, Aug 14, 2014 at 10:32 AM, Rusi Mody rustompm...@gmail.com wrote: To add to my earlier report: I managed to remove graphviz and its associated libraries. So that now aptitude dist-upgrade gives me only 1 'issue' : The following packages have unmet dependencies: systemd-sysv : Conflicts: sysvinit-core but 2.88dsf-53.3 is to be installed. The following actions will resolve these dependencies: Remove the following packages: 1) sysvinit-core You can either accept to remove sysvinit-core and run with systemd only or install systemd-shim and you won't be prompted to install systemd-sysv - and you'll be able to boot with sysvinit by default or systemd if you add init=/lib/systemd/systemd to the kernel cmdline. (the archives have this repeated a number of times!) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAOdo=SwotZ5w0JMb7aA2iU=3zickvooeakc-vacb_gis8l3...@mail.gmail.com
Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
On Thursday, August 14, 2014 9:10:02 PM UTC+5:30, Tom H wrote: On Thu, Aug 14, 2014 at 10:32 AM, Rusi Mody wrote: To add to my earlier report: I managed to remove graphviz and its associated libraries. So that now aptitude dist-upgrade gives me only 1 'issue' : The following packages have unmet dependencies: systemd-sysv : Conflicts: sysvinit-core but 2.88dsf-53.3 is to be installed. The following actions will resolve these dependencies: Remove the following packages: 1) sysvinit-core You can either accept to remove sysvinit-core and run with systemd only or install systemd-shim and you won't be prompted to install systemd-sysv - and you'll be able to boot with sysvinit by default or systemd if you add init=/lib/systemd/systemd to the kernel cmdline. (the archives have this repeated a number of times!) systemd-shim is currently installed Running with init=/bin/systemd makes networking stop working And /bin/systemd is softlinked to /lib/systemd/systemd so I guess that is a non-difference -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/efb5bddb-7a9b-43b1-b866-4074c70fb...@googlegroups.com
Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
Am 14.08.2014 16:02, schrieb Rusi Mody: On Thursday, August 14, 2014 3:40:03 PM UTC+5:30, Michael Biebl wrote: Am 14.08.2014 um 05:32 schrieb Rusi Mody: Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /dev/ppp device: No such file or directory Since you don't have the /dev/ppp device, I assume you are not using udev 208-7? Could you please post the version of udev (and systemd) you are using? Thanks Michael Just ran an aptitude update. After that: udev is at 208-6 which is the latest I see If you are using sysvinit as PID 1, upgrade udev to 208-7 (currently available from unstable) systemd is at 204-8 upgradable to 208-6 If you are using systemd as PID 1, you should avoid mixing udev 208 with systemd 204 and always upgrade both [1]. I'd suggest you install systemd-sysv (which will uninstall sysvinit-core) which will switch your default init to systemd. You will still have a fallback /lib/sysvini/init as long as the sysvinit package is installed and which you can use to boot the system in case the boot fails with systemd. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=75#35 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
On Thursday, August 14, 2014 3:40:03 PM UTC+5:30, Michael Biebl wrote: Am 14.08.2014 um 05:32 schrieb Rusi Mody: Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /dev/ppp device: No such file or directory Since you don't have the /dev/ppp device, I assume you are not using udev 208-7? Could you please post the version of udev (and systemd) you are using? Ok after dist-upgrade, box is at systemd 208-6 udev 208-6 libpam-systemd removed sysvinit, sysvinit-core, sysvinit-utils installed all at 2.88dsf-53.3 systemd-shim at 6-3 All show as latest. Does this look ok? I'll be checking if there is any improvement with booting with systemd. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e46f71d5-4ff2-49d4-be9c-2a57dfd77...@googlegroups.com
Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
On Thursday, August 14, 2014 10:10:02 PM UTC+5:30, Michael Biebl wrote: Am 14.08.2014 16:02, schrieb Rusi Mody: On Thursday, August 14, 2014 3:40:03 PM UTC+5:30, Michael Biebl wrote: Am 14.08.2014 um 05:32 schrieb Rusi Mody: Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /dev/ppp device: No such file or directory Since you don't have the /dev/ppp device, I assume you are not using udev 208-7? Could you please post the version of udev (and systemd) you are using? Thanks Michael Just ran an aptitude update. After that: udev is at 208-6 which is the latest I see If you are using sysvinit as PID 1, upgrade udev to 208-7 (currently available from unstable) systemd is at 204-8 upgradable to 208-6 If you are using systemd as PID 1, you should avoid mixing udev 208 with systemd 204 and always upgrade both [1]. I'd suggest you install systemd-sysv (which will uninstall sysvinit-core) which will switch your default init to systemd. You will still have a fallback /lib/sysvini/init as long as the sysvinit package is installed and which you can use to boot the system in case the boot fails with systemd. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=75#35 systemd is working (with handwritten grub line) Networking is back to automatically working I'll wait a bit before full switchover [Need to check printer etc Its often a source of trouble because Canon drivers are not the debian supplied ones ] Thanks again! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/25d2d1a3-fa23-4cc3-9478-f69be11f6...@googlegroups.com
Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
On Tuesday, August 12, 2014 3:20:02 PM UTC+5:30, Andrei POPESCU wrote: On Lu, 11 aug 14, 07:57:05, Rusi Mody wrote: If I start from grub using init=/bin/systemd it boots but networking does not work. Please attach the file 'bootlog' after running: journalctl -alb bootlog Thanks Andrei Tried doing that... does not seem to reach the list. So pruning down to what seems relevant and inlining below. Notes: 1. IPs have been masked. They 'look' ok (are not 192.168 types) 2. You asked flasgs -alb. The l does not seem valid. This is with -ab 3. Theres some resolvconf issue. There are bugs I see like https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244 But I dont know what changes with systemd. 4. The second bunch of lines probably comes from the manually given modprobe ppp pon dsl-provider --bootlog excerpt-- Aug 14 08:13:14 debian64 networking[418]: Configuring network interfaces...resolvconf: Error: /etc/resolvconf/run/interface either does not exist or is not a directory Aug 14 08:13:14 debian64 console-setup[444]: Setting up console font and keymap...done. Aug 14 08:13:14 debian64 systemd[1]: Started LSB: Set console font and keymap. Aug 14 08:13:14 debian64 networking[418]: resolvconf: Error: /etc/resolvconf/run/interface either does not exist or is not a directory Aug 14 08:13:14 debian64 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Aug 14 08:13:14 debian64 kernel: e100 :04:08.0 eth0: NIC Link is Up 100 Mbps Full Duplex Aug 14 08:13:14 debian64 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Aug 14 08:13:14 debian64 networking[418]: resolvconf: Error: /etc/resolvconf/run/interface either does not exist or is not a directory Aug 14 08:13:14 debian64 networking[418]: grep: /etc/resolv.conf: No such file or directory Aug 14 08:13:15 debian64 ntpdate[596]: Can't find host 0.debian.pool.ntp.org: Name or service not known (-2) Aug 14 08:13:15 debian64 ntpdate[596]: Can't find host 1.debian.pool.ntp.org: Name or service not known (-2) Aug 14 08:13:15 debian64 ntpdate[596]: Can't find host 2.debian.pool.ntp.org: Name or service not known (-2) Aug 14 08:13:15 debian64 ntpdate[596]: Can't find host 3.debian.pool.ntp.org: Name or service not known (-2) Aug 14 08:13:15 debian64 ntpdate[596]: no servers can be used, exiting Aug 14 08:13:15 debian64 pppd[594]: Plugin rp-pppoe.so loaded. Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /dev/ppp device: No such file or directory Aug 14 08:13:15 debian64 pppd[594]: Linux kernel does not support PPPoE -- are you running 2.4.x? Aug 14 08:13:15 debian64 pppd[594]: Exit. Aug 14 08:13:15 debian64 networking[418]: Plugin rp-pppoe.so loaded. Aug 14 08:13:15 debian64 networking[418]: Couldn't open the /dev/ppp device: No such file or directory Aug 14 08:13:15 debian64 networking[418]: Linux kernel does not support PPPoE -- are you running 2.4.x? Aug 14 08:13:15 debian64 networking[418]: Failed to bring up dsl-provider. Aug 14 08:13:15 debian64 ntpdate[632]: Can't find host 0.debian.pool.ntp.org: Name or service not known (-2) Aug 14 08:13:15 debian64 networking[418]: done. Further down the file Aug 14 08:13:48 debian64 sudo[957]: siva : TTY=tty1 ; PWD=/home/siva ; USER=root ; COMMAND=/sbin/modprobe pppoe Aug 14 08:13:48 debian64 sudo[957]: pam_unix(sudo:session): session opened for user root by siva(uid=0) Aug 14 08:13:48 debian64 kernel: PPP generic driver version 2.4.2 Aug 14 08:13:48 debian64 kernel: NET: Registered protocol family 24 Aug 14 08:13:48 debian64 sudo[957]: pam_unix(sudo:session): session closed for user root Aug 14 08:13:48 debian64 sudo[959]: siva : TTY=tty1 ; PWD=/home/siva ; USER=root ; COMMAND=/usr/bin/pon dsl-provider Aug 14 08:13:48 debian64 sudo[959]: pam_unix(sudo:session): session opened for user root by siva(uid=0) Aug 14 08:13:48 debian64 pppd[960]: Plugin rp-pppoe.so loaded. Aug 14 08:13:48 debian64 pppd[967]: pppd 2.4.6 started by siva, uid 0 Aug 14 08:13:48 debian64 sudo[959]: pam_unix(sudo:session): session closed for user root Aug 14 08:13:48 debian64 pppd[967]: PPP session is 10294 Aug 14 08:13:48 debian64 pppd[967]: Connected to 00:e0:fc:37:3c:02 via interface eth0 Aug 14 08:13:48 debian64 pppd[967]: Using interface ppp0 Aug 14 08:13:48 debian64 pppd[967]: Connect: ppp0 -- eth0 Aug 14 08:13:50 debian64 sudo[972]: siva : TTY=tty1 ; PWD=/home/siva ; USER=root ; COMMAND=/sbin/ifconfig Aug 14 08:13:50 debian64 sudo[972]: pam_unix(sudo:session): session opened for user root by siva(uid=0) Aug 14 08:13:50 debian64 sudo[972]: pam_unix(sudo:session): session closed for user root Aug 14 08:13:50 debian64 colord[760]: Automatic remove of LBP1210-Gray.. from cups-LBP1210 Aug 14 08:13:50 debian64 colord[760]: Profile removed: LBP1210-Gray.. Aug 14 08:13:50 debian64 colord[760]: device removed: cups-LBP1210 Aug 14 08:13:51 debian64 pppd[967]: CHAP authentication succeeded: Authentication success,Welcome! Aug 14 08:13:51 debian64
Re: networking fails with temporary systemd (was auto starting of ppp has stopped working)
On Lu, 11 aug 14, 07:57:05, Rusi Mody wrote: If I start from grub using init=/bin/systemd it boots but networking does not work. Please attach the file 'bootlog' after running: journalctl -alb bootlog Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
networking fails with temporary systemd (was auto starting of ppp has stopped working)
On Saturday, August 2, 2014 4:10:02 AM UTC+5:30, Michael Biebl wrote: Am 31.07.2014 20:27, schrieb Rusi Mody: After some recent upgrades (this is on jessie) auto starting of ppp has stopped working. So every time after booting I now have to run pppoeconf. Any ideas? This is a sysvinit specific problem [1]. Spefically, udev no longer creates dead devices notes which are used to trigger the auto-loading of kernel modules. Under systemd this is done properly, for sysvinit, we will need a workaround as in [2]. The solution is *not* to add the module to /etc/modules. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749021 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749021#10 Getting back to this since I have a bit of time... My system currently seems to be half way between systemd and init. ie by default process 1 is init; systemd seems to be there on the system but its not 1 by default If I start from grub using init=/bin/systemd it boots but networking does not work. I'd appreciate help on ironing this out and moving on to a full systemd install In more details: As earlier described on this thread: After some upgrade, the kernel modules related to ppp (some 3 or 4 of them) stopped being installed automatically. So from then on I am modprobing those and then manually running $ pon dsl-provider If however I boot grub with init=/bin/systemd then it does not work. ie - At start those modules remain non-loaded - modprobing them (seems to) load them in that they show in lsmod|grep ppp - Furthermore ifconfig seems to show a proper ppp0 inet addr after pon dsl-provider - But firefox cant find any page -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/43564f7b-9e00-4d29-8b3c-b8828442f...@googlegroups.com
