No Network connection after login failure

Kino · 2017-05-12 07:42:27

I don't know what happened, but...

I left the pc for a while and when I came back it had gone to the login screen. I was unable to log in - it would just not respond. So I startup up a laptop and checked these forums for a possible solution.
I found I could do a <ctrl><alt>F1 or F2 and startx did work but the image I use as background did not appear so I decided to reboot.

After reboot I noticed that one of my external hard drives was not responding - it turned out that the power supply to it had failed - and with a replacement power supply it worked fine (could this power supply failure cause the login problem? - I came across a mention of samba log files being a possible problem)

Anyhow, it did seem as if everything was working ok... BUT, when I tried to access my external hard drives from my other computer I could not make a connection.

Correction: I could not connect using BL on my other laptop but MS Windows did connect. Needless to say, I don't want to use MS Windows.

After some searching here: https://askubuntu.com/questions/754572/ … -is-masked

I tried some of these suggestions but I still get this:

systemctl restart samba
Failed to restart samba.service: Unit samba.service is masked.

Any help would be greatly appreciate

ector1935 · 2017-05-12 09:42:46

Hello,
I'm saying I do not use samba,I do not have any experience,we should understand why your samba is a mask,for now verifies samba, waiting for you know more than me.

testparm

Kino · 2017-05-12 17:33:19

OK, for what it's worth (I've omitted most of the service definitions - they're not a problem)

:~$ testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[printers]"
Processing section "[print$]"
Processing section "[Elements]"
Processing section "[TV_series]"
Processing section "[TV_series2]"
Processing section "[Anime2]"
Processing section "[TVseries3]"
Loaded services file OK.
Server role: ROLE_STANDALONE

Press enter to see a dump of your service definitions

# Global parameters
[global]
	server role = standalone server
	map to guest = Bad User
	obey pam restrictions = Yes
	pam password change = Yes
	passwd program = /usr/bin/passwd %u
	passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
	unix password sync = Yes
	syslog = 0
	log file = /var/log/samba/log.%m
	max log size = 1000
	dns proxy = No
	wins support = Yes
	usershare allow guests = Yes
	panic action = /usr/share/samba/panic-action %d
	idmap config * : backend = tdb

Head_on_a_Stick · 2017-05-12 18:12:38

Kino wrote:

I still get this:

systemctl restart samba
Failed to restart samba.service: Unit samba.service is masked.

Try:

sudo systemctl unmask samba.service

Disclaimer: I've never used Samba.

Kino · 2017-05-12 18:30:06

$ sudo systemctl unmask samba.service
[sudo] password for kino:

That had no effect on accessing the network.
So I tried:

:~$ sudo service samba stop
:~$ sudo service samba start
Failed to start samba.service: Unit samba.service is masked.

I'll try a reboot (again)

Kino · 2017-05-12 18:43:01

Well, that didn't work either.

:~$ service samba status
Failed to dump process list, ignoring: Unit samba.service is masked.
● samba.service
   Loaded: masked (/dev/null; bad)
   Active: inactive (dead)

and just to add to my confusion https://unix.stackexchange.com/question … cant-start

Head_on_a_Stick · 2017-05-12 18:52:13

Kino wrote:

https://unix.stackexchange.com/question … cant-start

Well, clearly I don't know what I'm talking about then

Good luck!

Kino · 2017-05-13 06:59:29

Well, it looks like I'm really screwed...

I removed samba via synaptic, re-installed it, rebooted and still:

service samba status
Failed to dump process list, ignoring: Unit samba.service is masked.
● samba.service
   Loaded: masked (/dev/null; bad)
   Active: inactive (dead)

The annoying thing is - I can access everything with MS Windows but not linux!

Short of re-installing BL (which would be a major pain) I don't know what else to try.

ohnonot · 2017-05-13 12:08:26

same computer as your last megathread? maybe related?

ector1935 · 2017-05-13 12:20:50

Hello,
try like this:

systemctl stop samba.service

systemctl disable samba.service

systemctl status samba.service

Once the status is disabled,I relaunched the link with:

systemctl start samba.service

If everything works with start, I'm back

systemctl enable samba.service

regards

Last edited by ector1935 (2017-05-13 12:22:01)

Horizon_Brave · 2017-05-13 17:34:23

ohnonot wrote:

your last megathread?

lol...

Kino · 2017-05-13 17:35:45

No joy

:~$ sudo systemctl disable samba.service
[sudo] password for kino: 
Synchronizing state of samba.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable samba
update-rc.d: error: samba Default-Start contains no runlevels, aborting.

and

:~$ systemctl status samba.service
Failed to dump process list, ignoring: Unit samba.service is masked.
● samba.service
   Loaded: masked (/dev/null; bad)
   Active: inactive (dead)

It's beginning to look like a fresh install is needed...

ector1935 · 2017-05-13 20:41:50

try fhis command:

rm -R /var/cache/samba/*

If it does not work out, try it

systemctl unmask samba
systemctl enable samba
systemctl restart samba

Kino · 2017-05-14 06:24:58

try fhis command:
rm -R /var/cache/samba/*

Already tried that - didn't work.
I've tried every option available with no success.
Today I shall reinstall the os.

ohnonot wrote:
your last megathread?

No - this is only one page (so far).
I think this was caused by sudden failure of an external hard drive which somehow caused the login screen to freeze.

ohnonot · 2017-05-14 10:45:05

Kino wrote:

ohnonot wrote:
your last megathread?
No - this is only one page (so far).
I think this was caused by sudden failure of an external hard drive which somehow caused the login screen to freeze.

you're misquoting me.
i was enquiring about the computer, not the length of the thread.

ector1935 · 2017-05-14 11:22:31

try this command and posted answer:

sudo systemctl enable smbd.service nmbd.service

Head_on_a_Stick · 2017-05-14 12:23:28

Is there anything relevant in the systemd journal?

Any errors will show up in red (if you use a decent $PAGER).

Kino · 2017-05-15 07:05:31

Well, I went ahead and re-installed BL and I now have a different problem:

smbstatus

Samba version 4.2.14-Debian
PID     Username      Group         Machine            Protocol Version       
------------------------------------------------------------------------------
Failed to initialize session_global: NT_STATUS_ACCESS_DENIED

Service      pid     machine       Connected at
-------------------------------------------------------
Failed to initialize session_global: NT_STATUS_ACCESS_DENIED
Failed to traverse sessions: NT_STATUS_ACCESS_DENIED

I have spent hours trying to find a solution - nothing seems to work!

try this command and posted answer:
sudo systemctl enable smbd.service nmbd.service

and

sudo systemctl enable smbd.service nmbd.service
[sudo] password for kino
Synchronizing state for smbd.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d smbd defaults
Executing /usr/sbin/update-rc.d smbd enable
Synchronizing state for nmbd.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d nmbd defaults
Executing /usr/sbin/update-rc.d nmbd enable

Result as above.

Is there anything relevant in the systemd journal?

My re-install did not upgrade systemd

systemd --version
systemd 215
+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR

so

sudo journalctl -b -1
[sudo] password for kino
Failed to look up boot -1: Cannot assign requested address

I thinkI now have a completely different problem from before.

Head_on_a_Stick · 2017-05-15 07:16:14

Kino wrote:

sudo journalctl -b -1
[sudo] password for kino
Failed to look up boot -1: Cannot assign requested address

But you only need to view the logs for the current boot — why are you attempting to read old logs?

ector1935 · 2017-05-15 07:53:08

Give an eye here,it would not hurt!:
https://ubuntuforums.org/archive/index. … 39668.html
Or here:
https://www.howtoforge.com/tutorial/deb … ba-server/

#1 2017-05-12 07:42:27

No Network connection after login failure

#2 2017-05-12 09:42:46

Re: No Network connection after login failure

#3 2017-05-12 17:33:19

Re: No Network connection after login failure

#4 2017-05-12 18:12:38

Re: No Network connection after login failure

#5 2017-05-12 18:30:06

Re: No Network connection after login failure

#6 2017-05-12 18:43:01

Re: No Network connection after login failure

#7 2017-05-12 18:52:13

Re: No Network connection after login failure

#8 2017-05-13 06:59:29

Re: No Network connection after login failure

#9 2017-05-13 12:08:26

Re: No Network connection after login failure

#10 2017-05-13 12:20:50

Re: No Network connection after login failure

#11 2017-05-13 17:34:23

Re: No Network connection after login failure

#12 2017-05-13 17:35:45

Re: No Network connection after login failure

#13 2017-05-13 20:41:50

Re: No Network connection after login failure

#14 2017-05-14 06:24:58

Re: No Network connection after login failure

#15 2017-05-14 10:45:05

Re: No Network connection after login failure

#16 2017-05-14 11:22:31

Re: No Network connection after login failure

#17 2017-05-14 12:23:28

Re: No Network connection after login failure

#18 2017-05-15 07:05:31

Re: No Network connection after login failure

#19 2017-05-15 07:16:14

Re: No Network connection after login failure

#20 2017-05-15 07:53:08

Re: No Network connection after login failure

Board footer