I just got an error message coming from wordpress saying on the index page that the connection to the database is not possible. I expected a problem in the connection chain but the real issue was related to a corrupted table in the database.
This as been fixed by repairing this table. So take care of the messages that can be wrong in the index page. The message in the admin index page was better concerning this point.
After I had to change a hard drive for another my linux Opensuse 12.2 grub bootloader was broken, here are some of the learning of this debugging phase :
– Restore grub to the new disk
– Start kernel manually
– Fix hard drive references
At the end, the process to recreate the bootloader and particularly to recreate the initrd file was broken, and I assume bugged. To really make it works, I had to update the whole Linux and again at the end of the process the booloader based on grub2 was impossible to execute. The solution was to select Grub (version 1) and it worked. I assume it was possible before update the whole distribution to use yast2 booloader and choose grub instead of grub2.
When you get a message like waiting for device … to apear at boot, it may be because of the initrd does not contain the right modules to access the hard drive. It appears when the motherboard has been changed.
This article is mostly notes taken during this debugging phase … so do not consider it as an howto but as a list of command and possible way to debug this kind of issues…
Sound a old hardware, but as it is not the first time I have issue to dump (tcpdump or wireshark) wifi connection on promiscuous mode, I prefer to write it once of all … It is not working !!!
If any of you have a solution to make it works, I’ll be happy to update this post. For the others, I expect you will loss less time searching and trying.
I’ve try to change the rights on the /dev/bfp* devices
I’ve try to use tcpdump -i en1 host xx.xx.xx.xx instead of wireshark
And at the end, I finally just got the broadcast traffic and the local traffic.
When your need to replicate data from one server to another, the rsync solution is usefull. It works over ssh and you do not really have any specific thing to configure. Here are the options to be used to get a full copy with all the rights and ownership replicated :
rsync -P -azc src_files_or_dir user@dest_server_ip:/dest_server_dir/
This works if the destination server have ssh open on port 22. If it is not the case another set of options is required :
rsync -P -azc -e "ssh -p dest_port" src_files_or_dir user@dest_server_ip:/dest_server_dir/
Hope it’ll help ! fro sure it will be a good reminder for me 😉
I had some trouble to install boinc application on OpenSuse 12.2 due to wxWidget configuration…
The right way tomake it work is to :
– Install wxWidgets-wxcontainer-compat-lib-config
– Install the libwx_xxxx_xxx-2_8-0-wxcontainer required (use ldd boincmgr to get the list)
– Create a symbolic link on libnotify.so.4 to libnotify.so.1 in /usr/lib64
After doing this, it worked for mand the following message has disapeared : symbol _ZTV16wxWindowListNode, version WXU_2.8 not defined in file libwx_gtk2u_core-2.8.so.0 with link time reference
To create a virtual IP on mac OS X, the command to be used is the following one, for example on the wifi interface :
sudo ifconfig en1 alias xx.xx.xx.xx/zz up when xx.xx.xx.xx is the expected IP address and zz the netmask
to remove the virtual interface replace alias by -alias option.
After installing the piratebox, it’s nice to customize it a little bit… There are many reason for this, the first one, in my point of view is to have a more understandable SSID name depend on your country… Here are the list of the step of the customizations I made on myne.
As promise, I’m looking for MR-3040 information about autonomy. This device is really interesting as it provides an internal battery to power the device on. The question was, how many time can we use it, is the autonomy good enough to have a real mobile device you don’t have to care about autonomy when bring out to public !
The first thing is to reload the battery, from 0 to 100% it takes 3:10 using the given equipment. The next thing is to empty the battery by just doing nothing else than switch it on, as a result, the MR-3040 ran during 7hours. This is a really good result as it means that we can bring it out most of one day (or night).
The last step is to empty the battery transferring file from & to to mr3040, in this scenario, the battery autonomy should be smaller but the result is an autonomy of 5 full hours with a transfer rate about 1.5MB/s. I was expecting a shorter time so it is a good news.
The main issue I can raised after this test is the coverage area of these kind of devices (MR3040 or MR3020) really limited to a some meters and really blocked by rock walls. This is limiting the share with the neighborhood capability. It makes it more recommended to have a share into a room.