[DCom] Live Content

[DCom] Live Content [Paid] 3.3.1

No permission to buy ($30.00)
    Nobody is reading this thread right now.
You need to stop the system service and change the configuration.
The launch commands have changed
Bash:
ExecStart=/usr/bin/php socket_server start -d
ExecStop=/usr/bin/php socket_server stop
ExecReload=/usr/bin/php socket_server restart

aha.... Almost :)

ExecStart=/usr/local/bin/php /home/nginx/domains/canadiancorvetteforums.com/public/socket_server.php start -d (code=exited, status=0/SUCCESS)


ccf_swoole.service: Can't open PID file /home/nginx/domains/mysite.com/public/src/addons/DCom/LiveContent/SocketServer/......

ccf_swoole.service: Main process exited, code=exited, status=255/EXCEPTION
 
Pay attention!!!
socket_server start -d

Gotcha, updated. Now server is running but unable to connect to front end. It's like it's not running.

Active: active (running) since Thu 2025-03-13 21:17:25 CDT; 1min 6s ago
Process: 3467 ExecStart=/usr/local/bin/php /home/nginx/domains/mysite.com/public/socket_server start -d (code=exited, status=0/SUCCESS)
 
----------------SWOOLE SERVER IS RUNNING----------------
Swoole version: 6.0.0 PHP version: 8.3.16
Start time 2025-03-14 02:17:25
Connection num 25
Abort count 0
Accept count 181
Close count 156
Worker num 20
Task worker num 0
User worker num 0
Idle worker num 19
Dispatch count 1049
Request count 1048
Response count 1128
Total recv bytes 91042
Total send bytes 45403
Pipe packet msg id 2490
Concurrency 1
Session round 181
Min fd 58
Max fd 91
Worker request count 82
Worker response count 89
Worker dispatch count 83
Worker concurrency 1
Coroutine num 3
Coroutine peek num 5
 
----------------SWOOLE SERVER IS RUNNING----------------
Swoole version: 6.0.0 PHP version: 8.3.16
Start time 2025-03-14 02:17:25
Connection num 25
Abort count 0
Accept count 181
Close count 156
Worker num 20
Task worker num 0
User worker num 0
Idle worker num 19
Dispatch count 1049
Request count 1048
Response count 1128
Total recv bytes 91042
Total send bytes 45403
Pipe packet msg id 2490
Concurrency 1
Session round 181
Min fd 58
Max fd 91
Worker request count 82
Worker response count 89
Worker dispatch count 83
Worker concurrency 1
Coroutine num 3
Coroutine peek num 5
1. Template modifications all applied.
2. Recheck group permissions, the permissions system has been changed.
 
1. Template modifications all applied.
2. Recheck group permissions, the permissions system has been changed.

1. Template mods all showing as applied
2. Registered group permission still applied for Real time...

Only thing is backend of XF still shows as Socket Server not running (though it is evidently).
 
1. Template mods all showing as applied
2. Registered group permission still applied for Real time...

Only thing is backend of XF still shows as Socket Server not running (though it is evidently).
Try stopping the socket server completely, check that no processes are listening on the port sudo lsof -i :2053 If there are listening processes, stop them kill -9 process number. Again check that no one is listening on the port, and then start the socket server.
 
1. Template mods all showing as applied
2. Registered group permission still applied for Real time...

Only thing is backend of XF still shows as Socket Server not running (though it is evidently).
You are stopping the socket server through a system service, right? systemctl stop livecontent
 
Correct. I stopped/started 3 times.

On the third time it finally started working on the front end at least. Very weird behaviour.

I ended up starting it raw php socker_server start -d instead of systemctl.... I can't explain it at the moment.

Oh wait I can reproduce this.

If I refresh this page /admin.php?add-ons/DCom-LiveContent/options (not save, just refresh it) when it still shows that server is not running in XF -> then it stops working on the front end?!?!?! Though the socket server itself is running.

If I don't use the page, it works???

Anyway I think there's a regression on the admin page from what I can tell.

It no longer shows status of socket server for swoole accurately and refreshing the page seems to disable push functionality through the server does continue to run. Let me know if you want access to figure this out.

Seems to be something from 3.2.5 onwards.

The what's new page updates do work though so that's good at least 👍
Thanks for being on top of it @DimmmCom
 
Last edited:
Oh wait I can reproduce this.

If I refresh this page /admin.php?add-ons/DCom-LiveContent/options (not save, just refresh it) when it still shows that server is not running in XF -> then it stops working on the front end?!?!?! Though the socket server itself is running.

If I don't use the page, it works???

Anyway I think there's a regression on the admin page from what I can tell.

It no longer shows status of socket server for swoole accurately and refreshing the page seems to disable push functionality through the server does continue to run. Let me know if you want access to figure this out.

Seems to be something from 3.2.5 onwards.

The what's new page updates do work though so that's good at least 👍
Thanks for being on top of it @DimmmCom
Send me the access details in direct messages and I'll check what the problem might be. I should be able to take a look in about 6-8 hours.
 
Back
Top