Question Plesk updates - Broken pipe error message

[Franco]

Hello,
I am running the latest Plesk 12.5 on the latest CentOs 6.8. Usually Plesk updates run fine, but every time I have the following messages a couple of times in the update log:

/usr/local/psa/bootstrapper/pp12.5.30-bootstrapper/bootstrapper.sh: line 345: $config.new: ambiguous redirect
cat: write error: Broken pipe
mv: target `/etc/httpd/conf/httpd.conf' is not a directory

I had that also with previous versions of Plesk and CentOs, thus I guess it's something in my config. Should I worry about it and is there a way to fix it, please?

Thanks
Franco

 

[IgorG]

Have you tried to fix it with

# plesk repair installation

?

 

[Franco]

hi, thanks for the suggestion. I think I treid it already, but I just run it again and I can see the same error. The full repair log:

Reconfiguring the Plesk installation

Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
===> Cumulative upgrade and repair of APS controller database has been completed.
===> Cumulative APS controller upgrade and repair (final stage) has been started.
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /usr/local/psa/bootstrapper/pp12.5.30-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf)
WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf)
rndc: connect failed: 127.0.0.1#953: connection refused
Reconfiguring mail subsystem...
Reconfiguring Apache web server...
/usr/lib64/plesk-9.0/services/webserver.apache: line 466: $config.new: ambiguous redirect
cat: write error: Broken pipe
mv: target `/etc/httpd/conf/httpd.conf' is not a directory
/usr/lib64/plesk-9.0/services/webserver.apache: line 466: $config.new: ambiguous redirect
cat: write error: Broken pipe
mv: target `/etc/httpd/conf/httpd.conf' is not a directory
/usr/lib64/plesk-9.0/services/webserver.apache: line 466: $config.new: ambiguous redirect
cat: write error: Broken pipe
mv: target `/etc/httpd/conf/httpd.conf' is not a directory
[Tue Jul 05 10:53:18 2016] [warn] module security2_module is already loaded, skipping
[Tue Jul 05 10:53:18 2016] [warn] module unique_id_module is already loaded, skipping
Reconfiguring ProFTPD FTP server...
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
Reconfiguring SSL ciphers and protocols...
Regenerating web servers' configuration files...
Cleaning active Panel sessions...

Bootstrapper repair finished.

 

[IgorG]

Do you have Plesk installation on Virtozzo VPS or it is standalone server?
I would suggest you check that filesystem is not corrupted. Also make sure that there is no lack of free diskspace or inodes.

 

[Franco]

It's a VPS on VMware.
I ran last night an fsck on the main partition (sda1) and all looks fine, but the error is sitll there.
There seems to be plenty of inodes free still. The disk space looks ok, except on those tmpfs and devtmpfs

Filesystem Size Used Avail Use% Mounted on
rootfs 23G 14G 8.4G 62% /
devtmpfs 927M 156K 927M 1% /dev
tmpfs 939M 0 939M 0% /dev/shm
/dev/sda1 23G 14G 8.4G 62% /

Not sure what all those devices are, do you think I should check further?
I also have an ftp mapped NFS drive with plenty of space and inodes. Works fine but it forces me to update D_DUMP at every Plesk upgrade (but that's another story...)