-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mosquitto last update does NOT start any more if Websockets port is defined #4210
Comments
The port is not the problem, the protocol is the problem |
Thanks BenjV ... this seems a logical explanation ... but why would SynoCommunity do this for their new version if the previous did have websockets working well ? |
Don't no. |
Hi together, The mosquitto.log says: |
It seems to be a Mosquitto problem and not a SynoCommunity issue. They say it is fixed, so a new build for this package to upgrade to version 1.6.12 should fix this. |
Hi all, is there any possibility to download the previous stable version 1.4.14-9 (?) as a .spk file for manual install on the Synology ? |
https://synocommunity.com/package/mosquitto Download the version you want and do a manual install |
as I read it, it was fixed in 1.6.11... I will try and see if I can compile it myself and see if websockets gets compiled in by default or not. |
Maybe you should read the whole thread before posting already posted information. |
lol my bad. Anyway trying to rebuild the package myself right now to see if I can fix the problem. |
@arnebjarne can you confirm this is fixed with my latest commit? |
Hi hgy59. I think i still miss some of you patches I will double check your big commit from mosquotto 1.4 to 1.6.12 I get back. |
Hi hgy59. I can confirm that your latest commit ( https://github.com/ymartin59/spksrc/tree/4044_update_mosquitto ) make mosquitto 1.6.12-10 compile with websockets on arch-rtd1296. I have the version running on my DS418. |
* mosquitto: update to 1.6.12 * fix configure options (similar to #4196) * changes not already commited on #4068 - updated libwebsockets - fix clock_gettime for arm5 and older ppc - install mosquitto_rr too - update icon * use current config file * support ppc853x by patch * Fix openssl install for CMake to detect it * fix make options #4210 * final fix for openssl 1.0.1 - remove openssl.cnf from PLIST as it was removed by using installed /etc/ssl/openssl.cnf Co-authored-by: hgy59 <[email protected]>
@BenjV , thanks for the link to the downloads of old versions. |
There is no difference for DSM 6.1 and DSM 6.2 packages, they are all compatible. But the package is already upgraded to 1.6.12-10 so manual download is not needed anymore. |
Update 1.6.12-11 published and tested with |
* mosquitto: update to 1.6.12 * fix configure options (similar to SynoCommunity#4196) * changes not already commited on SynoCommunity#4068 - updated libwebsockets - fix clock_gettime for arm5 and older ppc - install mosquitto_rr too - update icon * use current config file * support ppc853x by patch * Fix openssl install for CMake to detect it * fix make options SynoCommunity#4210 * final fix for openssl 1.0.1 - remove openssl.cnf from PLIST as it was removed by using installed /etc/ssl/openssl.cnf Co-authored-by: hgy59 <[email protected]>
For new Package Requests, see the guidelines
Setup
Package Name: Mosquitto
Package Version: 1.6.12-10
NAS Model: DS1019+
NAS Architecture: DSM 6.2.3-25426 Update 2
DSM version: DSM 6.2.3-25426 Update 2
After updating my longtime GOOD WORKING previous Mosquitto version (1.4.14-9 ??) to the latest 1.6.12-10 it refused to start and gave an error: "Failed to run the package service"
De-install and re-install with default .conf settings was running fine with this newest version.
However ... when I add an extra listener on port 9001 websockets this latest version refused to start giving the same above message.
=================================================================
Extra listeners
=================================================================
AFTER UPGRADE on 5-10-2020 "Extra listeners" next 2 lines were giving ERROR: "Failed to run the package service" !!! ???
listener 9001
protocol websockets
#=================================================================
Changing the port number to other values than 9001 did not solve the problem.
The text was updated successfully, but these errors were encountered: