Diet Bos's questions

GoodDay all,

New day, new linux adventures on my home server:

Can resolvconf-pull-resolved.path be blocking my servers internet connection ?

Background info:

I updated/upgraded my server to the latest updates recently, following the routine execution of apt update && apt upgrade and went to work.

Later I was trying to ssh to my server on the static IP address I have for it, but there was no connection. Figured I needed to reboot the server and I should be good to go again and ran off again. Sometime later I ssh again to the server, still found no connection to host. By then I got worried.

Booting the system while looking to the screen I noticed the first [FAILED] to be resolvconf-pull-resolved and a bit later unable to bring op networking (second [FAILED]).

Tried some stuff already like this page, but that did not help.

Tried journalctl -xe and got a lot of stuff in red. But I did not seem to get to the bottom of why this is happening.

So now I am wondering if there are 2 problems, or that it is 1 problem that leads to another. As I know my around Linux a bit to do basic stuff, this is way above my knowledge.

Any pointers are well appreciated and I would like to say thanks in advance for any help.

I already have a new live USB stick hanging around for reinstalling the server, but then again, what is the fun in that.

PS: Other intel information on my server can be found Here.

Where I have an update hold on libtevent > hope that there is no version conflict

So again, can somebody shed light on this?

EDIT:

systemctl status resolvconf-pull-resolved.path

● resolvconf-pull-resolved.path Loaded: loaded (/lib/systemd/system/resolvconf-pull-resolved.path; enabled; vendor preset: enabled) Active: inactive (dead) Jan 22 21:46:48 rabbithole systemd1: resolvconf-pull-resolved.path: Refusing to start, unit to trigger not loaded. Jan 22 21:46:48 rabbithole systemd1: Failed to start resolvconf-pull-resolved.path.

systemctl status resolvconf-pull-resolved.service

● resolvconf-pull-resolved.service Loaded: error (Reason: Invalid argument) Active: inactive (dead)

systemctl status resolvconf.service

● resolvconf.service - Nameserver information manager Loaded: loaded (/lib/systemd/system/resolvconf.service; enabled; vendor preset: enabled) Active: active (exited) since Tue 2019-01-22 21:46:47 CET; 4min 10s ago Docs: man:resolvconf(8) Process: 545 ExecStart=/sbin/resolvconf --enable-updates (code=exited, status=0/SUCCESS) Process: 538 ExecStartPre=/bin/touch /run/resolvconf/postponed-update (code=exited, status=0/SUCCESS) Process: 535 ExecStartPre=/bin/mkdir -p /run/resolvconf/interface (code=exited, status=0/SUCCESS) Main PID: 545 (code=exited, status=0/SUCCESS) CGroup: /system.slice/resolvconf.service Jan 22 21:46:47 rabbithole systemd1: Starting Nameserver information manager... Jan 22 21:46:47 rabbithole systemd1: Started Nameserver information manager. Jan 22 21:46:47 rabbithole resolvconf[545]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf

So, at first Samba worked even after the update, Due to lack of GB on server side hard drive i changed the label of a drive. altered all i needed to relevant places and files. All worked, could acces from windows laptop and linux laptop.

After a couple of days i noticed drives were not mounted on my linux laptop. thinked not to much of it yet. My wife complaints that the server is unreachable and now after investigating i ran out of options :

tail -f /var/log/kernel.log

gave the following in the beginning :

Oct 15 21:43:07 Laptop kernel: [ 3910.412985] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
Oct 15 21:43:07 Laptop kernel: [ 3910.418005] CIFS VFS: Error connecting to socket. Aborting operation.
Oct 15 21:43:07 Laptop kernel: [ 3910.418016] CIFS VFS: cifs_mount failed w/return code = -111

so i changed /etc/fstab entry and added :

/media/movies cifs auto,*`vers=1.0`*,credentials=/etc/samba/user,noexec 0 0

which only left me with :

Oct 15 21:49:06 Laptop kernel: [ 4269.887208] CIFS VFS: Error connecting to socket. Aborting operation.
Oct 15 21:49:06 Laptop kernel: [ 4269.887218] CIFS VFS: cifs_mount failed w/return code = -111

So i got the version right, but now it leaves me with return code -111 which google says basicly anything can be wrong.

On the server side : service smb status gives

>● smb.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

service smbd status
>● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd)
   Loaded: loaded (/etc/init.d/smbd; bad; vendor preset: enabled)
   Active: active (exited) since Mon 2018-10-15 21:11:36 CEST; 43min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1136 ExecStart=/etc/init.d/smbd start (code=exited, status=0/SUCCESS)
Oct 15 21:11:38 rabbithole smbd[1159]:    #10 /usr/sbin/smbd(main+0x1899) [0x55c64af04099]
Oct 15 21:11:38 rabbithole smbd[1159]:    #11 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f410b059b97]
Oct 15 21:11:38 rabbithole smbd[1159]:    #12 /usr/sbin/smbd(_start+0x29) [0x55c64af04199]
Oct 15 21:11:38 rabbithole smbd[1159]: [2018/10/15 21:11:38.090690,  0] ../source3/lib/util.c:801(smb_panic_s3)
Oct 15 21:11:38 rabbithole smbd[1159]:   smb_panic(): calling panic action [/usr/share/samba/panic-action 1159]
Oct 15 21:11:38 rabbithole smbd[1159]: [2018/10/15 21:11:38.098636,  0] ../source3/lib/util.c:809(smb_panic_s3)
Oct 15 21:11:38 rabbithole smbd[1159]:   smb_panic(): action returned status 0
Oct 15 21:11:38 rabbithole smbd[1159]: [2018/10/15 21:11:38.098738,  0] ../source3/lib/dumpcore.c:303(dump_core)
Oct 15 21:11:38 rabbithole smbd[1159]:   dumping core in /var/log/samba/cores/smbd
Oct 15 21:11:38 rabbithole smbd[1159]: 

probably everybody notices the obvious, but my knowledge is not that great, so i hope people here know some other solutions or maybe give me pointers as i think this goes beyond novice level :)

Maybe the best advise is to copy /etc/samba/smb.conf and re install samba. or run an alternative (is there any?)

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 16-10-2018 added:

looks more and more that the server side isn't available : when using

sudo smbclient -L //server_ip -U user

i get prompted for user password which after i am certain i added the correct password :

WARNING: The "syslog" option is deprecated
Enter diet's password: 
Connection to 192.168.178.21 failed (Error NT_STATUS_CONNECTION_REFUSED)

Added more :

When command nmblookup is performed on client side, the server does not show, tried various variations of the command, but the servers ip address did not show. smbtree also gives no server.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ADDED 18-10-2018

I have been digging deeper into the panic reaction and looked into the log files /var/log/samba/log.nmdb where i found the following

diet@rabbithole:~$ sudo cat /var/log/samba/log.nmbd 
[2018/10/15 21:11:36.244286,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2018/10/15 21:11:36.244592,  0] ../lib/util/fault.c:78(fault_report)
  ===============================================================
[2018/10/15 21:11:36.244651,  0] ../lib/util/fault.c:79(fault_report)
  INTERNAL ERROR: Signal 11 in pid 1135 (4.3.11-Ubuntu)
  Please read the Trouble-Shooting section of the Samba HOWTO
[2018/10/15 21:11:36.244708,  0] ../lib/util/fault.c:81(fault_report)
  ===============================================================
[2018/10/15 21:11:36.244750,  0] ../source3/lib/util.c:789(smb_panic_s3)
  PANIC (pid 1135): internal error
[2018/10/15 21:11:36.245703,  0] ../source3/lib/util.c:900(log_stack_trace)
  BACKTRACE: 11 stack frames:
   #0 /usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0(log_stack_trace+0x1a) [0x7f58521627aa]
   #1 /usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0(smb_panic_s3+0x20) [0x7f5852162880]
   #2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7f585445ff1f]
   #3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x1b136) [0x7f5854460136]
   #4 /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7f58548c4890]
   #5 /usr/lib/x86_64-linux-gnu/libtalloc.so.2(talloc_get_size+0x5) [0x7f58517005a5]
   #6 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(event_add_to_poll_args+0x76) [0x7f5853846556]
   #7 /usr/sbin/nmbd(listen_for_packets+0xff) [0x5590a81f47af]
   #8 /usr/sbin/nmbd(main+0xcf6) [0x5590a81e3bb6]
   #9 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f5850cfbb97]
   #10 /usr/sbin/nmbd(_start+0x29) [0x5590a81e3f79]
[2018/10/15 21:11:36.245966,  0] ../source3/lib/util.c:801(smb_panic_s3)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 1135]
[2018/10/15 21:11:36.259765,  0] ../source3/lib/util.c:809(smb_panic_s3)
  smb_panic(): action returned status 0
[2018/10/15 21:11:36.260473,  0] ../source3/lib/dumpcore.c:303(dump_core)
  dumping core in /var/log/samba/cores/nmbd
[2018/10/16 22:25:50.464532,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2018/10/16 22:25:50.501751,  0] ../lib/util/fault.c:78(fault_report)
  ===============================================================
[2018/10/16 22:25:50.501817,  0] ../lib/util/fault.c:79(fault_report)
  INTERNAL ERROR: Signal 11 in pid 1069 (4.3.11-Ubuntu)
  Please read the Trouble-Shooting section of the Samba HOWTO
[2018/10/16 22:25:50.501886,  0] ../lib/util/fault.c:81(fault_report)
  ===============================================================
[2018/10/16 22:25:50.501927,  0] ../source3/lib/util.c:789(smb_panic_s3)
  PANIC (pid 1069): internal error
[2018/10/16 22:25:50.502887,  0] ../source3/lib/util.c:900(log_stack_trace)
  BACKTRACE: 11 stack frames:
   #0 /usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0(log_stack_trace+0x1a) [0x7f58a6df07aa]
   #1 /usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0(smb_panic_s3+0x20) [0x7f58a6df0880]
   #2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7f58a90edf1f]
   #3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x1b136) [0x7f58a90ee136]
   #4 /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7f58a9552890]
   #5 /usr/lib/x86_64-linux-gnu/libtalloc.so.2(talloc_get_size+0x5) [0x7f58a638e5a5]
   #6 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(event_add_to_poll_args+0x76) [0x7f58a84d4556]
   #7 /usr/sbin/nmbd(listen_for_packets+0xff) [0x5626ea7dc7af]
   #8 /usr/sbin/nmbd(main+0xcf6) [0x5626ea7cbbb6]
   #9 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f58a5989b97]
   #10 /usr/sbin/nmbd(_start+0x29) [0x5626ea7cbf79]
[2018/10/16 22:25:50.503153,  0] ../source3/lib/util.c:801(smb_panic_s3)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 1069]
[2018/10/16 22:25:50.512666,  0] ../source3/lib/util.c:809(smb_panic_s3)
  smb_panic(): action returned status 0
[2018/10/16 22:25:50.512764,  0] ../source3/lib/dumpcore.c:303(dump_core)
  dumping core in /var/log/samba/cores/nmbd
[2018/10/18 19:44:06.860935,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2018/10/18 19:44:06.894869,  0] ../lib/util/fault.c:78(fault_report)
  ===============================================================
[2018/10/18 19:44:06.894939,  0] ../lib/util/fault.c:79(fault_report)
  INTERNAL ERROR: Signal 11 in pid 1046 (4.3.11-Ubuntu)
  Please read the Trouble-Shooting section of the Samba HOWTO
[2018/10/18 19:44:06.894998,  0] ../lib/util/fault.c:81(fault_report)
  ===============================================================
[2018/10/18 19:44:06.895041,  0] ../source3/lib/util.c:789(smb_panic_s3)
  PANIC (pid 1046): internal error
[2018/10/18 19:44:06.896034,  0] ../source3/lib/util.c:900(log_stack_trace)
  BACKTRACE: 11 stack frames:
   #0 /usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0(log_stack_trace+0x1a) [0x7f1e44bbf7aa]
   #1 /usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0(smb_panic_s3+0x20) [0x7f1e44bbf880]
   #2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7f1e46ebcf1f]
   #3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x1b136) [0x7f1e46ebd136]
   #4 /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7f1e47321890]
   #5 /usr/lib/x86_64-linux-gnu/libtalloc.so.2(talloc_get_size+0x5) [0x7f1e4415d5a5]
   #6 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(event_add_to_poll_args+0x76) [0x7f1e462a3556]
   #7 /usr/sbin/nmbd(listen_for_packets+0xff) [0x55ff3c5c47af]
   #8 /usr/sbin/nmbd(main+0xcf6) [0x55ff3c5b3bb6]
   #9 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f1e43758b97]
   #10 /usr/sbin/nmbd(_start+0x29) [0x55ff3c5b3f79]
[2018/10/18 19:44:06.896297,  0] ../source3/lib/util.c:801(smb_panic_s3)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 1046]
[2018/10/18 19:44:06.906076,  0] ../source3/lib/util.c:809(smb_panic_s3)
  smb_panic(): action returned status 0
[2018/10/18 19:44:06.906178,  0] ../source3/lib/dumpcore.c:303(dump_core)
  dumping core in /var/log/samba/cores/nmbdADDED 18-10-2018

Google Led me to bugzilla where i find "exactly" the same fault codes.

Now is the question, how do i get this solved? how do i downgrade to libtevent 0.9.28 to see if this gets it fixed?

i found this page so i know it is in older repositories, which i added but when i use

diet@rabbithole:~$ sudo apt-get install libtevent-dev=0.9.28-0ubuntu0.14.04.1 

i get

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libtevent-dev : Depends: libtevent0 (= 0.9.28-0ubuntu0.14.04.1) but 0.9.34-1 is to be installed
E: Unable to correct problems, you have held broken packages.

Although i think i am on to something, i am wondering why i am having this issue after updating to 18.04. the buzilla report dates from a while back with solutions mentioned that i cannot roll out yet because off my lack of skills to do a rollback on a package and its dependencies.

On previous installed version kubuntu 15.xx i added a line into /etc/rc.local - /home/diet/scripts/my-auto-mount-script which obviously referred to a script that if on home wifi network drives should be mounted.

This worked flawlessly on kubuntu 15.xx

After the upgrade it seems /etc/rc.local is being ignored on boot because running the command /etc/rc.local still seems to do the trick. The reason I think rc.local is being ignored is because the script it refers to should produce logs on script success but also on script fail, but there are no logs.

Can anyone give me some pointers on how to troubleshoot this matter?

PS : yes I know that putting stuff in /etc/fstab is also a way of mounting the drives, but when I'm not at home I hate it that I can see the drives on dolphin and have those little red crosses on them because the are not there. This way when I'm on the road (it is a laptop) people can't see what i have at home.

Fglrx Not working after install (I know)

HW : Asus K72j with AMD HD5470 laptop

So, after installing the ATI drivers fglrx on my ASUS K72J laptop via CL my screen booted black.

So at first I thought I had broken my computer and had to make a fresh install. After using my wifes laptop I found out fglrx does something with the backlight. Also I thought it might have something to do with me running 14.10 instead of 14.04.

Since I really wanted the drivers to work (using garmin basecamp on windows vmware) I figured I had to reinstall (I am a noob) 14.04.

So after making a fresh install of 14.04 I sudo apt myself to the latest available fglrx drivers in the repo's just to find out that I booted a black screen again. Using my wifes laptop I found out that fglrx still(or also)has problems with the backlight in 14.04

With a torch and settings set to high contrast I could somewhat work my way through some stuff and one was that the fglrx drivers were working properly, I could even launch the catalyst control centre. Just to see everything was working perfect, except backlight.

So with a torch I worked myself through some webpages and solutions which all did not work. I sudo apt xbacklight – which installed fine – adjusting did not work.

looking at /sys/class/backlight/acpi_video0 i could see all brightness settings seems to be as they should be.(at least as i think they are allright)

furthermore I used this page as a reference :

After installing fglrx on Ubuntu 14.04 there is no backlight (hd 5470). Is there any workaround?

Short list of things on the page :

• Try adding acpi_backlight=legacy or acpi_backlight=vendor (not both) as a kernel parameter. (in GRUB, with the update GRUB command afterwards)
• sudo apt-get install xbacklight, then set xbacklight XX
• xrandr --output LVDS1 --brightness 0.9
• sudo setpci -s 00:02.0 F4.B=xx ( this does not work because I thing my - - VGA is on 00:01.0 using that in the command does not help)
• video.use_native_backlight=1(or 0) in grub with no result

some things that i have noticed: I disabled quiet boot in GRUB, so i can see the boot phase quite verbose. everything works fine, but just before the login screen appears the screen goes black.

Further I have used the page

https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Debugging_information_to_provide_in_your_bug_report

and used the techniques provided. Which all lead me to thing there is actually nothing wrong with the settings. The backlight just does not come alive with the drivers installed/loaded.

Creating the udev rule mention on this wiki did also not work for me (maybe I did something wrong , not sure if I had to udevstart before reboot)

https://wiki.archlinux.org/index.php/backlight

But that refers to arch linux not ubuntu ( allthough I tried some things from that wiki as well)

Looking at the xorg.conf i notice that even with the removed fglrx drivers the screen should use fglrx drivers

Section "Device"

Identifier "aticonfig-Device[0]-0"

Driver "fglrx"

BusID "PCI:1:0:0"

This might be because i did not generate a new xorg.conf file after i purged the fglrx driver?

So, using dmesg > dmesg.txt i cannot really find a difference in using the fglrx driver or without using the fglrx driver

Both state

[ 21.231381] asus_laptop: Asus Laptop Support version 0.42

[ 21.232100] asus_laptop: BSTS called, 0x5800 returned

[ 21.232121] asus_laptop: model detected

[ 21.232599] asus_laptop: Backlight controlled by ACPI video driver

there are lots of differences between the 2, but since i was looking for backlight issues this might be the most important lines?

-Is there anybody who can help me out a little more, or give me a push in the right direction in solving the issue? (except using the ubuntu drivers) -is there an option that i need to know about with the fglrx drivers to enable the backlight?