[SOLVED] cannot create /opt/zimbra/data/tmp/zmcontrol.out.XXYn2

[vortex566]

I came into work this morning to find the following error, while trying to start the zmcontrol service. This must have happen after 02:30 during the night, as we have last nights back-up.

sh: cannot create /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: Read-only file system

Starting logger...sh: cannot create /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: Read-only file system
cat: /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: No such file or directory
Failed.

Starting mailbox...sh: cannot create /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: Read-only file system
cat: /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: No such file or directory
Failed.

Starting antispam...sh: cannot create /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: Read-only file system
cat: /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: No such file or directory
Failed.


Starting antivirus...sh: cannot create /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: Read-only file system
cat: /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: No such file or directory
Failed.

Starting snmp...sh: cannot create /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: Read-only file system
cat: /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: No such file or directory
Failed.

Starting spell...sh: cannot create /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: Read-only file system
cat: /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: No such file or directory
Failed.

Starting mta...sh: cannot create /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: Read-only file system
cat: /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: No such file or directory
Failed.

Starting stats...sh: cannot create /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: Read-only file system
cat: /opt/zimbra/data/tmp/zmcontrol.out.XXYn2: No such file or directory
Failed.

[uxbod]

Do you use local or SAN based storage ? Does /var/log/messages should anything ? What does dmesg show ?

[vortex566]

A restart of the server seems to have fixed the problem. Just trying to see why it happen now.

[Smakodak]

I have that same issue, and a reboot didn't help. I have searched through the logs, but I haven't been able to find anything relating to this. It's weird because the /tmp folder has drwxrwxrwt permissions, so it should be writeable?!
Does anyone have an idea.

I have this error as well. I don't know if they are related...
"Use of uninitialized value $current_proto in string eq at /usr/lib/perl/5.10/Sys/Syslog.pm line 371"
"Use of uninitialized value $current_proto in string eq at /usr/lib/perl/5.10/Sys/Syslog.pm line 374"

I'm running this version as a ESXi 4 virtual machine.
Release 7.0.0_GA_3077.UBUNTU10_64 UBUNTU10_64 FOSS edition

Can anyone help?

Kind regards Anders

[iway]

Do you have space left on the device?

[Smakodak]

Hi iway

Thank you for responding.

Yes, there is plenty of space left.
System load: 0.21 Processes: 180
Usage of /: 17.6% of 51.45GB Users logged in: 0
Memory usage: 52% IP address for eth0: 192.168.100.2
Swap usage: 0%

-Anders

[iway]

What was the solution?

[infortica]

Hello!

Write permission problem occurs because during shutdown or reboot the system is set read-only files.
This happens before stopping Zimbra.

For solutions to the problem, change the order of call scripts in the directories:
/etc/rc0.d/ (shutdown)
/etc/rc6.d/ (reboot)

eg: change @89zimbra the @10zimbra

Zimbra stop before setting the file system for read-only.


"Use of uninitialized value $current_proto in string eq at
/usr/lib/perl/5.10/Sys/Syslog.pm line 371"
"Use of uninitialized value $current_proto in string eq at
/usr/lib/perl/5.10/Sys/Syslog.pm line 374"

The problem can be solved by giving the initial values ​​of the variable "$current_proto" eg $current_proto = 0; instead of # undef;
in the file "/ usr/lib/perl/5.10/Sys/Syslog.pm"


Bartłomiej Kapica
infortica.pl

Originally Posted by Smakodak

I have that same issue, and a reboot didn't help. I have searched through the logs, but I haven't been able to find anything relating to this. It's weird because the /tmp folder has drwxrwxrwt permissions, so it should be writeable?!
Does anyone have an idea.

I have this error as well. I don't know if they are related...
"Use of uninitialized value $current_proto in string eq at /usr/lib/perl/5.10/Sys/Syslog.pm line 371"
"Use of uninitialized value $current_proto in string eq at /usr/lib/perl/5.10/Sys/Syslog.pm line 374"

I'm running this version as a ESXi 4 virtual machine.
Release 7.0.0_GA_3077.UBUNTU10_64 UBUNTU10_64 FOSS edition

Can anyone help?

Kind regards Anders

[meuchel]

Sorry for my ignorance in reviving this old thread but I recently ran into this issue.
I was able to fix the read only by following your advice on correcting the shutdown order.
but i still get the $current_proto error. Where in the file should we set it equal to 0?
do you have an exerpt?

[infortica]

Hi,
in section Global Variables, it is 95 line in file /usr/lib/perl/5.10/Sys/Syslog.pm