cannot use screen command at boot

Bug #1310270 reported by Nick Sillito
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
screen (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have just upgraded from Ubuntu Server 13.10 to 14.04 (64 bit).

I have a script that I use to run a minecraft server (for my son, honest) that uses the screen command. This worked fine using ubuntu 13.10, but now fails on 14.04.

When I run the command during the /etc/init.d process, I get the message:

"Cannot make directory '/var/run/screen': Permission denied" when I use the screen command.

When I list the directory, at the same time (ls -l /var/run), I get:

lrwxrwxrwx 1 root root 4 Apr 20 12:26 /var/run -> /run

If I run the command once the system has finished booting, it all works fine.

If I give the command ls -l /var/run, once the booting has finished, I get:

-rw-r--r-- 1 root root 24995 Apr 20 12:45 alternatives.log
-rw-r--r-- 1 root root 15562 Apr 20 12:46 apps4new.log
-rw-r--r-- 1 root root 140924 Apr 20 12:43 apps4new.log~
drwxr-xr-x 2 root root 4096 Apr 20 12:27 apt
-rw-r----- 1 syslog adm 43009 Apr 20 15:00 auth.log
-rw-r--r-- 1 root root 5640 Apr 20 14:20 boot.log
-rw-r--r-- 1 root root 61649 Apr 16 23:03 bootstrap.log
-rw-rw---- 1 root utmp 0 Apr 16 23:02 btmp
drwxr-xr-x 2 root root 4096 Apr 20 12:38 cups
drwxr-xr-x 2 root root 4096 Apr 12 06:33 dist-upgrade
-rw-r----- 1 root adm 51832 Apr 20 14:19 dmesg
-rw-r----- 1 root adm 51914 Apr 20 14:15 dmesg.0
-rw-r----- 1 root adm 14618 Apr 20 14:11 dmesg.1.gz
-rw-r----- 1 root adm 14605 Apr 20 14:02 dmesg.2.gz
-rw-r----- 1 root adm 14623 Apr 20 13:47 dmesg.3.gz
-rw-r----- 1 root adm 14610 Apr 20 13:17 dmesg.4.gz
-rw-r--r-- 1 root root 516026 Apr 20 12:46 dpkg.log
-rw-r--r-- 1 root root 32032 Apr 20 12:45 faillog
-rw-r--r-- 1 root root 1259 Apr 20 12:42 fontconfig.log
drwxr-xr-x 2 root root 4096 Apr 20 12:26 fsck
drwxr-xr-x 3 root root 4096 Apr 20 12:34 installer
-rw-r----- 1 syslog adm 612031 Apr 20 14:20 kern.log
drwxr-xr-x 2 landscape root 4096 Apr 20 12:34 landscape
-rw-rw-r-- 1 root utmp 292292 Apr 20 14:27 lastlog
drwxr-xr-x 2 ntp ntp 4096 Oct 9 2013 ntpstats
drwxr-xr-x 3 root root 4096 Apr 20 14:48 samba
drwxr-xr-x 2 squeezeboxserver nogroup 4096 Apr 20 12:45 squeezeboxserver
-rw-r----- 1 syslog adm 687760 Apr 20 15:02 syslog
-rw-r--r-- 1 root root 247920 Apr 20 14:19 udev
drwxr-xr-x 2 root root 4096 Apr 20 12:50 unattended-upgrades
drwxr-xr-x 2 root root 4096 Apr 20 13:18 upstart
-rw-rw-r-- 1 root utmp 52992 Apr 20 14:27 wtmp

Revision history for this message
UbuntuAddicted (ubuntuaddictedubu) wrote :

this is a duplicate bug but they specifically told us to report a new bug against 14.04. I'm running Xubuntu 14.04.1 and I have an init.d script called minecraft which has the following screen command
as_user "cd $MCPATH && /usr/bin/screen -dmS survival-mc /usr/bin/java -Xms2048M -Xmx2048M -Djava.net.preferIPv4Stack=true -XX:MaxPermSize=128M -XX:UseSSE=3 -XX:-DisableExplicitGC -XX:+UseParallelOldGC -XX:ParallelGCThreads=4 -XX:+AggressiveOpts -XX:+UseCompressedStrings -jar $SERVICE nogui"

and I can see in the boot up messages the following error
"Cannot make directory '/var/run/screen': Permission denied" when I use the screen command.

How do I fix this please?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in screen (Ubuntu):
status: New → Confirmed
Revision history for this message
Kyle Crist (zecixx) wrote :

Sorry if this is not appropriate but I have the exact same problem. I just added

/etc/init.d/minecraft start

to

/etc/rc.local

Not ideal, but a workaround none the less is better than having upset customers.

We were told in https://bugs.launchpad.net/ubuntu/+source/screen/+bug/574773 to start a new bug, and this shows confirmed but its been a while, and I know my 12.04 system did not have this behavior. I'd be happy to provide logs and the script contents if needed. Thanks for the community support :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.