Dattobd not working on Ubuntu Server 16.04.1 #47
Comments
|
The messages from server A are normal. They are simply messages indicating usage errors. Server B is a kernel panic which is a much more serious problem. In your case, this is almost definitely the result of having updated your kernel without rebooting your machine. DKMS tries to build kernel modules for every installed and running kernel, but in an effort to save space / work it has a feature called "weak modules" that tries to detect whether 2 installed kernels are similar enough that they can use the same kernel module. Unfortunately, dattobd has to do some unusual things (namely hooking into the syscall table) which DKMS fails to account for. In the end, it tries to use the kernel module for the running kernel for the installed kernel, which promptly causes a crash. The solution is simply to uninstall dattobd, reboot your machine (which will cause the system to use latest installed kernel) and then reinstall dattobd. We should have a paragraph about this in the troubleshooting section, so I will leave this issue open until we get around to it. |
|
We already tried reinstalling before but it did not help, I have now done the following: After these commands I receive slightly different errors: |
|
Looks like you are still getting a kernel panic. Can you post the output from |
|
|
What are the outputs of |
|
|
If you get the problem in init of the module, it's a kernel mismatch like tom said. On August 24, 2016 8:55:57 AM EDT, Codyksp notifications@github.com wrote:
|
|
Look in /lib/modules for weak-modules On August 24, 2016 10:03:54 AM EDT, Codyksp notifications@github.com wrote:
|
|
The modules folder contains 4.4.0-31-generic and 4.4.0-34-generic. I can't find anything called weak-modules anywhere on the server. |
|
A |
|
|
Do you have any kind of antivirus running on that server? |
|
None that I am aware of, no. |
|
Reproduced on Fedora 23. |
|
I only see it on Fedora 23 and Fedora 24, which are now running the 4.7.3 kernel. Unable to reproduce anywhere else (including Arch running 4.7.3). |
|
I have an idea what's going on, still flushing out details. Tom will work it out in seconds, I expect. On September 15, 2016 4:06:50 PM EDT, Tim Crawford notifications@github.com wrote:
|
|
@Codyksp can you try with the latest commit? |
|
Same results as before, as far as I can see. UrBackup doesn't receive a file list and dattobd shows the same errors. I completely uninstalled both UrBackup Client and dattobd before installing them again. I actually had some trouble removing dattobd aswell, it was giving me errors about dkms and hanging. |
|
Hmmmm. I'm sorry for the trouble you've been having and I'm sorry we can't seem to reproduce the issue on our end. A couple of last things that could help us debug the issue if you can spare the time and are ok with allowing us to crash the machine one more time:
to this: and then running
This line will probably be slightly different when you run it this time.
That will output the 5 lines of code around the line that caused the crash along with the line number itself. Paste that output here and then you can quit out of gdb just by entering |
|
Hello Tom, Thank you for the extra support, however we are currently moving to a different backup/restore solution for our linux servers as we also some running on Arch Linux which don't properly support dattobd (or UrBackup for that matter). I'm sorry that I can't try your last solution to troubleshoot this further but we have spent too much time on this and have found a solution that meets our needs for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have recently installed dattobd to be used together with UrBackup to make full file backups with a snapshot. We have 2 Ubuntu servers, both the same version. One server works fine and the other one won't even start a backup.
I have only performed a fresh install of UrBackup (choosing dattobd) and a fresh installation of dattobd according to the install file.
The following is output from dmesg on both servers:
Server A (working):
I don't know what the last 4 errors mean (or if they even matter) but the backups are working fine.
Server B (not working):
I have absolutely no idea what these messages mean but they don't look good to me.
Here is also the log output from UrBackup on the working server:
The text was updated successfully, but these errors were encountered: