The officially official Devuan Forum!

You are not logged in.

#1 2022-10-02 07:51:13

tux
Member
Registered: 2022-10-01
Posts: 36  

[SOLVED] boot error

deleted a /tmp, app was not working,  app is not reason for error.

on reboot
error at checking misc settings
pre-flight check error
unable to write to path temp_fil ('temp') permission denied

after enter name and pass says failed to execute login command

tried recovery boot, same error.

booted installer medium to see partishon that boot has regenerated /tmp file

do not want to reinstall, want to learn to how to fix

Last edited by tux (2022-10-02 07:51:56)

Offline

#2 2022-10-02 14:49:14

tux
Member
Registered: 2022-10-01
Posts: 36  

Re: [SOLVED] boot error

can get past login/pass in old recovery mode, black screen and bash. nmcli ifconfig cannot connet wifi.

how connect wifi via command line?

/tmp dir did have a socks that was there after every boot, might be call lo.socks?

could be nagios, remove by installer?

Offline

#3 2022-10-02 16:36:07

chris2be8
Member
Registered: 2018-08-11
Posts: 168  

Re: [SOLVED] boot error

First try ls -ld /tmp/ Output should look like

drwxrwxrwt 10 root root 16384 Oct  2 17:30 /tmp/

If it's missing then as root mkdir /tmp and chmod 1777 /tmp and see if that fixes it. If it exists but perms are not drwxrwxrwt enter the chmod.

Offline

#4 2022-10-02 18:42:27

tux
Member
Registered: 2022-10-01
Posts: 36  

Re: [SOLVED] boot error

/mnt$ ls -ld /tmp/
drwxrwxrwt 9 root root 220 Oct  2 18:25 /tmp/

chmod set to 755

in recovery mode

sudo startx launch output
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
and fatel sever error
(EE) could not create lock file in /tmp/.tx0-lock
xinit unable to connect to x server
connection refused

Offline

#5 2022-10-02 20:11:39

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 779  

Re: [SOLVED] boot error

Perhaps / is mounted read-only due to filesystem errors?

If so, you probably need to boot up with another root filesystem so as to fsck the root partition first.

Or you might try to remount / read-write.

Another option is to mount a tmpfs onto /tmp. Though that might not be enough as it won't allow log files or authority files to be written.

Offline

#6 2022-10-03 14:56:28

Head_on_a_Stick
Member
From: London
Registered: 2019-03-24
Posts: 2,737  

Re: [SOLVED] boot error

Create a new /tmp/ & /var/tmp/ with

install -dv -m 1777 /tmp /var/tmp

Reference: https://www.linuxfromscratch.org/lfs/vi … gdirs.html

Last edited by Head_on_a_Stick (2022-10-03 14:56:49)


"Who's the idiot in charge?" — ralph.ronnquist

Offline

#7 2022-10-03 17:52:23

tux
Member
Registered: 2022-10-01
Posts: 36  

Re: [SOLVED] boot error

could chmod 644 directories conflict with 1777 /tmp cause boot error?

is devuan install default directories chmod 644?

Last edited by tux (2022-10-03 19:09:36)

Offline

#8 2022-10-03 21:14:00

tux
Member
Registered: 2022-10-01
Posts: 36  

Re: [SOLVED] boot error

removed unused server daemon and packages for apache and nagio unneeded

boot gives no more errors, same for recovery mode

but after enter name and pass says     failed to execute login command

and recovery mode no longer has error (EE) could not create lock file in /tmp/.tx0-lock
but new error output from startx launch
xinit: Connection to xserve lost

Offline

#9 2022-10-04 15:42:16

Head_on_a_Stick
Member
From: London
Registered: 2019-03-24
Posts: 2,737  

Re: [SOLVED] boot error

Please post the full content of ~/.local/share/xorg/Xorg.0.log (or any other Xorg.?.log if you ran startx from a different TTY).


"Who's the idiot in charge?" — ralph.ronnquist

Offline

#10 2022-10-06 17:46:45

tux
Member
Registered: 2022-10-01
Posts: 36  

Re: [SOLVED] boot error

Solution
recovery mode

chmod
install -dv -m 1777 /tmp

mount -o remount,rw /
X -configure

rm -f /tmp/.x* another alternative is  rm -f /tmp/.X0-lock*

check if program is using dbus
grep -r dbus /etc/systemd/system/*

if the answer is yes
sudo service <program name> start
logout

login interface, sign in
back to normal, run sudo apt-get update, upgrade, dist-upgrade, autoremove, autoclean
restart.

developers - synaptic nagios package might be creating a persistent .sock in /tmp

Offline

Board footer