Issue Cannot start event handler: Could not decode JSON, syntax error - malformed JSON.

[W.c]

Hello,

in the current Plesk Obsidian release 18.0.36 I'm getting an error message regarding not started event handlers/malformed JSON when updating a domain via CLI.

For example:

# plesk bin domain --update domain.tld -perl false
SUCCESS: Update of domain 'domain.tld' completed.
[2021-06-22 09:54:41.465] 84512:60d197410cb9f ERR [panel] Cannot start event handler: Could not decode JSON, syntax error - malformed JSON.

There is an event handler set up for the "Physical hosting updated" event that seems to cause this issue:

# plesk bin event_handler --list
   Id               1
   Name             Physical hosting updated
   Priority         50
   User             root
   Command          /usr/local/bin/phys_hosting_update_handler.sh

The phys_hosting_update_handler.sh script simply writes the current date into a file, so there is not much magick going on here:

#!/bin/bash
/usr/bin/date > /var/www/vhosts/system/${NEW_DOMAIN_NAME}/conf/last_update.txt

Despite the error message the handler script still is executed when updating a domain via CLI (as you can easily see in this case by checking the date in the last_update.txt file). So it doesn't make much sense why this message appears at all.

Any idea how I can get rid of these "Cannot start event handler" messages?

 

[sebgonzes]

Hello, have same issue with last MU...

[2021-06-23 09:24:40.716] 449:60d2e1b82af17 ERR [panel] Cannot start event handler: Could not decode JSON, syntax error - malformed JSON.

Please plesk team and @IgorG , need an solution.

 

[IgorG]

Have you tried to put into Event Command not bash script but target command '/usr/bin/date > /var/www/vhosts/system/${NEW_DOMAIN_NAME}/conf/last_update.txt'?

 

[sebgonzes]

Have you tried to put into Event Command not bash script but target command '/usr/bin/date > /var/www/vhosts/system/${NEW_DOMAIN_NAME}/conf/last_update.txt'?

@IgorG , we have not try nothing, but these command works without problem since various years and now have an failure since the last MU.

 

[IgorG]

@IgorG , we have not try nothing, but these command works without problem since various years and now have an failure since the last MU.

Submit Reports in this case.

 

[sebgonzes]

Submit Reports in this case.

done, thanks @IgorG !