• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Forwarded to devs Cannot start event handler: Could not decode JSON, syntax error - malformed JSON.

S

sebgonzes

Silver Pleskian
Username: sebgonzes

TITLE

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

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

obsidian 18.0.36, cloudlinux 7, x86_64

PROBLEM DESCRIPTION

Since the last MU, we have error from event_handler (we are the second client to report bug yet, these same event_handler are working since various years yet) :

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

STEPS TO REPRODUCE

The error in our case is updating an hosting with cli :

/usr/local/psa/bin/subscription -u 'XXXX.com' -hard_quota '50M'

SUCCESS: Update of domain 'XXXX.com' completed.
[2021-06-23 09:24:40.716] 449:60d2e1b82af17 ERR [panel] Cannot start event handler: Could not decode JSON, syntax error - malformed JSON.

The event is simple in our case :

/usr/local/psa/admin/bin/php /path/to/own/phpscript.php domain update <new_domain_name>

ACTUAL RESULT

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

EXPECTED RESULT

No error return

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Thank you!
Could you please:
  • Show the current output of systemctl status plesk-task-manager
  • Enable debug in /usr/local/psa/admin/conf/panel.ini

    [taskManager]
    debug = 1
    [debug]
    enabled = 1
    [log]
    filter.priority = 7
    show.util_exec = on

  • Enable debug in /usr/local/psa/admin/conf/task-manager.yml and run systemctl restart plesk-task-manager

    log:
    level: DEBUG

  • Trigger the event handler
  • Provide the /var/log/plesk/panel.log and /var/log/plesk/task-manager.log files
 
IgorG said:
Thank you!
Could you please:
  • Show the current output of systemctl status plesk-task-manager
  • Enable debug in /usr/local/psa/admin/conf/panel.ini

    [taskManager]
    debug = 1
    [debug]
    enabled = 1
    [log]
    filter.priority = 7
    show.util_exec = on

  • Enable debug in /usr/local/psa/admin/conf/task-manager.yml and run systemctl restart plesk-task-manager

    log:
    level: DEBUG

  • Trigger the event handler
  • Provide the /var/log/plesk/panel.log and /var/log/plesk/task-manager.log files
Click to expand...
Ok, can you provide an email to send info? or any other private way?
 
According to developers, the issue is caused by PPPM-13048. No real impact except errors.
 
IgorG said:
According to developers, the issue is caused by PPPM-13048. No real impact except errors.
Click to expand...
Great, hope they will able to remove message in next MU (we control any error message in our system and had now to make an manual check every time)

Thanks
 
Hi @IgorG reviewing last MU

Plesk Obsidian 18.0.37​

, very very disappointed to see that this bug not seem solved! It can be "just" an detail, but very annoying to who check logs!
 
This is very annoying, currently we are not able to upgrade from 18.0.35 to a higher version due to this error because this is breaking
all our E2E provisioning calls, please fix this ASAP (support mentioned that this is planned to be included in the next release 18.0.37)!


cheers Michael
 
And because of this case we are not able to upgrade to 18.0.37 (PPPM-13048 - not marked as solved) - on the other side Plesk
needs to think about the Support Policy because of this two newer releases now on (since 18.0.37 release 18.0.35 not supported anymore officially)

...

cheers Michael
 
After update to Plesk 18.0.37 shows error below, but 18.0.36 doesn't, any hints?

Bash: 
# plesk bin admin --disable-access-domain
SUCCESS: Plesk is now accessible only over the port 8443.
PHP Fatal error:  Uncaught JMS\Serializer\Exception\RuntimeException: Could not decode JSON, syntax error - malformed JSON. in /usr/local/psa/admin/plib/vendor/jms/serializer/src/JsonDeserializationVisitor.php:240
Stack trace:
#0 /usr/local/psa/admin/plib/vendor/jms/serializer/src/Serializer.php(245): JMS\Serializer\JsonDeserializationVisitor->prepare('')
#1 /usr/local/psa/admin/plib/vendor/jms/serializer/src/Serializer.php(180): JMS\Serializer\Serializer->visit(Object(JMS\Serializer\GraphNavigator\DeserializationGraphNavigator), Object(JMS\Serializer\JsonDeserializationVisitor), Object(JMS\Serializer\DeserializationContext), '', 'json', 'Plesk\\Task\\Mana...')
#2 /usr/local/psa/admin/plib/Task/Manager.php(72): JMS\Serializer\Serializer->deserialize('', 'Plesk\\Task\\Mana...', 'json')
#3 /usr/local/psa/admin/plib/WebServerManager/Adapter/AsyncReconfiguration.php(49): Plesk\Task\Manager->createTask(Object(Plesk\Task\Manager\Request))
#4 /usr/local/psa/admin/plib/WebServerManager/Adapter/AsyncReconfiguration.php(21): WebServerMa in /usr/local/psa/admin/plib/vendor/jms/serializer/src/JsonDeserializationVisitor.php on line 240
exit status 255
 
nethubonline said:
After update to Plesk 18.0.37 shows error below, but 18.0.36 doesn't, any hints?

Bash: 
# plesk bin admin --disable-access-domain
SUCCESS: Plesk is now accessible only over the port 8443.
PHP Fatal error:  Uncaught JMS\Serializer\Exception\RuntimeException: Could not decode JSON, syntax error - malformed JSON. in /usr/local/psa/admin/plib/vendor/jms/serializer/src/JsonDeserializationVisitor.php:240
Stack trace:
#0 /usr/local/psa/admin/plib/vendor/jms/serializer/src/Serializer.php(245): JMS\Serializer\JsonDeserializationVisitor->prepare('')
#1 /usr/local/psa/admin/plib/vendor/jms/serializer/src/Serializer.php(180): JMS\Serializer\Serializer->visit(Object(JMS\Serializer\GraphNavigator\DeserializationGraphNavigator), Object(JMS\Serializer\JsonDeserializationVisitor), Object(JMS\Serializer\DeserializationContext), '', 'json', 'Plesk\\Task\\Mana...')
#2 /usr/local/psa/admin/plib/Task/Manager.php(72): JMS\Serializer\Serializer->deserialize('', 'Plesk\\Task\\Mana...', 'json')
#3 /usr/local/psa/admin/plib/WebServerManager/Adapter/AsyncReconfiguration.php(49): Plesk\Task\Manager->createTask(Object(Plesk\Task\Manager\Request))
#4 /usr/local/psa/admin/plib/WebServerManager/Adapter/AsyncReconfiguration.php(21): WebServerMa in /usr/local/psa/admin/plib/vendor/jms/serializer/src/JsonDeserializationVisitor.php on line 240
exit status 255
Click to expand...
in our case, this error appear since update to 18.0.36 and unfortunately have not been solved yet in last MU (18.0.37) that was what we needed...
 
You must log in or register to reply here.

Similar threads

W
Issue Cannot start event handler: Could not decode JSON, syntax error - malformed JSON.
Replies
5
Views
2K
sebgonzes
S
Hangover2
Forwarded to devs Upgrade to 18.0.37 fails in step TrimPlanNames
Replies
6
Views
2K
IgorG
IgorG
C
Issue pum is called with arguments: ['--list', '--repo-info', '--json']
Replies
4
Views
3K
VNick
V
Quinten
Resolved Reverse Proxy server (Nginx) won't start after renewing a domains certificate
Replies
7
Views
8K
Quinten
Quinten
burnley
Forwarded to devs wp-toolkit maintenance cron error: SQLSTATE[23000]: Integrity constraint violation: 19 UNIQUE constraint failed
Replies
1
Views
2K
IgorG
IgorG
Back
Top