Skip to content
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

Baikal compatibility issues with DSM 6.2.3 #4

Closed
spoo333 opened this issue Jun 27, 2020 · 4 comments · Fixed by #5
Closed

Baikal compatibility issues with DSM 6.2.3 #4

spoo333 opened this issue Jun 27, 2020 · 4 comments · Fixed by #5
Assignees
Labels

Comments

@spoo333
Copy link

spoo333 commented Jun 27, 2020

Hello,

Thank you for providing Baikal packages.

When I install Baikal 0.4.6-001 on DSM 6.2.3-25426, I get the following error message in the Synology's Notifications section: "DSM cannot start up normally because it ran into a problem. Please contact the Synology support team for help." The moment I remove the Baikal package, everything works fine again and the message disappears. If I reboot the NAS before removing the Baikal packages, i cannot log into the Synology's web interface via the modified http and https ports - it sets itself to the defaults 5000 and 5001 ports.

Is Baikal not compatible with DSM 6.2.3 or is there a setting I can change to avoid the scenario above?

Thanks,
David

@LaurentMarchelli
Copy link
Owner

Hi spoo333,

The issue is a bit odd as it seems to appear on DS718+ but not on DS211, even if both have the same DSM version 6.2.3-2.
What is your Synology Model ?

It is even worse if you have redirected the http port to the https, as you do not have anymore access to the DSM, the only way is to uninstall the package from the command line, if you hopefully activated the ssh.

synopkg uninstall baikal

I apologize for the inconvenience, I'm working on the bug fix.
I keep u informed,

Best regards,
Laurent Marchelli

@spoo333
Copy link
Author

spoo333 commented Aug 15, 2020 via email

@LaurentMarchelli
Copy link
Owner

Hi spoo333,

Thank you for your feed back, as the issue is now solved, it will benefit to all.

Best regards,
Laurent Marchelli

@spoo333
Copy link
Author

spoo333 commented Aug 20, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants