the “Timeout waiting for PADO packets” hassle

Sep 2 09:56:21 maia pppd[2805]: Timeout waiting for PADO packets
Sep 2 09:56:21 maia pppd[2805]: Unable to complete PPPoE Discovery
Sep 2 09:57:26 maia pppd[2805]: Timeout waiting for PADO packets
Sep 2 09:57:26 maia pppd[2805]: Unable to complete PPPoE Discovery
Sep 2 09:58:31 maia pppd[2805]: Timeout waiting for PADO packets
Sep 2 09:58:31 maia pppd[2805]: Unable to complete PPPoE Discovery
Sep 2 09:59:36 maia pppd[2805]: Timeout waiting for PADO packets
Sep 2 09:59:36 maia pppd[2805]: Unable to complete PPPoE Discovery
Sep 2 10:00:41 maia pppd[2805]: Timeout waiting for PADO packets
Sep 2 10:00:41 maia pppd[2805]: Unable to complete PPPoE Discovery
Sep 2 10:01:46 maia pppd[2805]: Timeout waiting for PADO packets
Sep 2 10:01:46 maia pppd[2805]: Unable to complete PPPoE Discovery
Sep 2 10:01:46 maia pppd[2805]: Exit.


Your error log looking like this? Be sure to double check with your ISP if bridge has been enabled

Read More

One command away from hell :D

So there I was cleaning out the e-mail server (Postfix running on Debian), and I noticed that a lot of customers have their trash folder with up to 6 GB of data in them. Since e-mail server was running out of space I decided to clean it up.
So I proceed casually to type in the following while in the trash directory..
root@XYXY:/rm *

rm: cannot remove `bin’: Is a directory
rm: cannot remove `boot’: Is a directory
rm: cannot remove `dev’: Is a directory
rm: cannot remove `emul’: Is a directory
rm: cannot remove `etc’: Is a directory
rm: cannot remove `home’: Is a directory
rm: cannot remove `initrd’: Is a directory
rm: cannot remove `lib’: Is a directory
rm: cannot remove `lost+found’: Is a directory
rm: cannot remove `media’: Is a directory

The one thing that went through my mind is…Sh** – what a massive fu** up

After panicking for a hour or two…started from bits and pieces to pull it all back together.

Fortunately I had a pretty updated backup on a another server and that eased my mind because it wasn’t a total disaster – I just had to find a way to start up the VM that I had successfully deleted.

I took a look at the other VM I had running and copied their boot – I knew I was going to need this because , I have realised (after A LOT of googling 😀 ) that I removed /lib64 and /lib32 (which are symlinks to /lib).
Thus disabling me from executing any command because it depends on /lib64/ld-linux-x86-64.so.2.

Here’s the part where I got lucky and saved my sorry a** :)

So there is this one file that is tatically linked on the system – and it doesn’t need any libs (/lib64) – and that is the /lib/ld-linux-x86-64.so.2 file.
If you use this file you can force ln command to check out /lib for the libs instead of the missing (deleted by yours truly) /lib64.

So all you need to do is type in /lib/ld-linux-x86-64.so.2-library-path /lib /bin/ln-sf/lib /lib64
Which in fact recreates the /lib64 symlink… HURRAY 😀

Read More