Weird PPPOE issue at boot time.

I've noticed this message lately and thought nothing of it because my internet still worked.?? Last night I had to run the PPPOE config again to get it to work.??

Thanks for the reply. Ok, so you have had the same issue I have. But how do I fix it. I hate having to run pppoeconf every time I log into Mepis, I shouldn't have to. Plus, I never had to do this with Mepis 2004.06, I thinl my /etc/ppp/ppp_on_boot.dsl?? and my ppp_on_boot file got damaged. there semas to be nothing in it. What is weird is that pppoecoonf doesn't update that file and, the clock error at the begining durring boot about not finding a host name happens before pppd loads. Plus I don't get any error besides ppp_on_boot and everything else seams to be ok. Any body know how to fix, or even better, what is suposed to be in that file for my DSL to start up automaticaly at boot?

I'll try that and see if that works. Thanks for your post. If copying and pasting what you have to the file I am asking about in question doesn't fix anythuing or eliminate any errors, then I'll post here and we'll take it from there. Thanks again for replying loyed230. We shall see.

I fixed my file as sugested thank you and that eliminated some of the errors but i still get this:

Mon Mar 14 22:24:37 2005: Running 0dns-down to make sure resolv.conf is ok...done.
Mon Mar 14 22:24:37 2005: Setting up networking...done.
Mon Mar 14 22:24:37 2005: Cleaning up /var/run/pppX-up files that might have been left by pppstatus .
Mon Mar 14 22:24:37 2005: Setting up IP spoofing protection: rp_filter.
Mon Mar 14 22:24:37 2005: Configuring network interfaces...Plugin rp-pppoe.so loaded.Mon Mar 14 22:24:40 2005: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.3
Mon Mar 14 22:24:40 2005: done.
Mon Mar 14 22:24:40 2005: Starting portmap daemon: portmap.
Mon Mar 14 22:24:41 2005: ^[]R^[[9;30]^[[14;30]
Mon Mar 14 22:24:42 2005: Setting the System Clock using the Hardware Clock as reference...
Mon Mar 14 22:24:43 2005: System Clock set. Local time: Mon Mar 14 22:24:43 EST 2005

Mon Mar 14 22:24:43 2005: Running ntpdate to synchronize clockError : Temporary failure in name resolution.
Mon Mar 14 22:24:43 2005: Initializing random number generator...done.
Mon Mar 14 22:24:43 2005: Setting up guarddog firewall...done.
Mon Mar 14 22:24:44 2005: Recovering nvi editor sessions... done.
Mon Mar 14 22:24:44 2005: Setting up X server socket directory /tmp/.X11-unix....done.
Mon Mar 14 22:24:45 2005: INIT: Entering runlevel: 5
Mon Mar 14 22:24:45 2005: Starting system log daemon: syslogd.
Mon Mar 14 22:24:45 2005: Starting kernel log daemon: klogd.
Mon Mar 14 22:24:45 2005:************************************************************************************
Mon Mar 14 22:24:45 2005: * /etc/ppp/ppp_on_boot is deprecated. Please configure your system to use
Mon Mar 14 22:24:45 2005: * the standard /etc/network/interfaces method.
Mon Mar 14 22:24:45 2005: * You can consult /usr/share/doc/ppp/README.Debian.gz and interfaces(5)
Mon Mar 14 22:24:45 200Mon Mar 14 22:24:45 2005: *
5: * for details.Mon Mar 14 22:24:45 2005: * This message has been printed by /etc/init.d/ppp .
Mon Mar 14 22:24:45 2005: ************************************************************************************
Mon Mar 14 22:24:50 2005: Starting up PPP link: pppdPlugin rp-pppoe.so loaded.
Mon Mar 14 22:24:50 2005: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.3
Mon Mar 14 22:24:50 2005: .
Mon Mar 14 22:24:50 2005: Starting portmap daemon: portmap.

This is an epcert from my bootlog. Again, I have to run pppoeconf every time I reboot, once I log in. I shouldn;t have to and never did with simplymepis 2004.x. Anyway, it is weird it calims pppoe is loaded fine but you see the clock sync error and also once logged in I can ping or get any host anmes to work even tough all the information is there in the corect config files including my user and password for login to my isp for DSL. But for soe reason I need to run pppoeconfig every time. Again I shouldn't have to pppoeconf should save my data and settings and automaticaly start at boot properly.

Any more help would be apreciated. Thanks. I am usingh simplymepis 3.3 currently.

All, I don't have DSL at home, I use cable; however, when you mention a "timing problem" Ben, it brings this question to my mind: All of the applications that are run during startup/shutdown are controlled by symbolic links in the /etc/rc*d directories, where "*" is the "run-level" of the system at the time. As the system is booting, it goes up from Single-user to multi-user through each of these run-levels.

Enough "education" for our viewers (grin). Ben, other than /etc/init.d/guarddog, what are some of the other scripts that are run to get DSL running? The "timing" might be controlled by changing some/all /etc/rc*d links from S45 to S50 or S40 for example. In other words, it may be necessary to adjust when a particular script is started. Since you're more knowledgable about what scripts are needed for DSL, perhaps you can show their names here. If so, then check what run-levels and sequence each of them has. You can do that from a command line by entering:

ls -la /etc/rc*d/*someprogram*

This will give you a list with entries such as
/etc/rcS.d/S45someprogram
(there will be more)

Then, if one DSL control program is starting before (or after) it should, then we can change the link to start after (or before)...

Just a thought with as much value as the pixels they're written on

Jon

Ben:

Yes, do a little research and get back to me.

On my system, guarddog is started as "S65" in the "Single User" mode. However, you may be able to put the scripts you need before (after?) that. If it's "S70something" simply rename it to "S62something". If there's already an "S62somethingelse" that doesn't matter, as long as "S62something" doesn't overwrite a previous "S62something"

Jon

Good to hear back from you Ben. Glad you got it working. Yes, when in doubt, take a little nap

Don't ya love open-source!

Jon