• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Zend Log Exception > not possible to reach the login page of Plesk

janm

New Pleskian
Hi everyone,

we suddenly gets this message when we are open the login url into one of our Plesk servers.
At the moment we have no clue why this happen and therefore I am asking for a hint how we can solve it.

ERROR: Uncaught Zend_Log_Exception: Unable to write to stream in /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Log/Writer/Stream.php:135 Stack trace: #0 /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Log/Writer/Abstract.php(88): Zend_Log_Writer_Stream->_write(Array) #1 /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Log.php(464): Zend_Log_Writer_Abstract->write(Array) #2 /opt/psa/admin/plib/Plesk/Log.php(265): Zend_Log->log('Unable to write...', 3, Array) #3 /opt/psa/admin/plib/Plesk/Log.php(168): Plesk_Log::log('panel', 3, 'Unable to write...') #4 /opt/psa/admin/plib/PleskException.php(26): Plesk_Log::err('Unable to write...') #5 /opt/psa/admin/plib/PleskException.php(13): report_crash('Unable to write...', Array, 'Zend_Log_Except...', 500, Object(Zend_Log_Exception)) #6 [internal function]: plesk_exception_handler(Object(Zend_Log_Exception)) #7 {main} thrown (Stream.php:135)

I tried to find something by using the search function but it was not successful.
 

Attachments

  • Bildschirmfoto 2022-03-27 um 14.04.12.png
    Bildschirmfoto 2022-03-27 um 14.04.12.png
    157.8 KB · Views: 1
Have you tried to fix it with

# plesk repair installation

?
 
Also, make sure that you have enough free disk space on your partitions.
 
that was the solution
Also, make sure that you have enough free disk space on your partitions.
after we did a restart, the error message disappeared. Then we checked the free space on the server.. and the problem was the backup routine. The space was more or less 100% full. After we created some free space, everything is working fine now. Thanks for looking into our issue!
 
Back
Top