-
-
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
Ejabberd not starting after installation #2260
Comments
same here. tried to start it from commandline. here is the output:
|
after adding a ejabberd user manually i get this error:
|
same here, I think ejabberd package is not compatible with this version of dsm. |
@Dr-Bean is this package still being maintained? I would be willing to post a bounty if it would help. |
Same here, not starting. Is there any fix? |
So is there a solution. I cannot start the package ejabberd either. |
Not starting for me either on Synology DSM 6.1 Update 1 on DS213j. Anyone got some workarounds maybe? |
Bummer, I was so looking forward to running this for secure internal messaging. |
posted a small bounty to see if we can get this running again. |
This problem still exists as of February 23. I have a new Synology NAS and I tried to install ejabberd, but it won't start, even if I try to manually start it in the Package Center. Edit: I have added to the bounty. |
I had the same problem, which disappeared after rebooting the synology. |
It is version 2.1.13. Released 25 Jun 2013..... Current is 18.09. I'm afraid this project is dead. Sorry, I cannot help, have not done any compiling since Algol60 in the early 1970ties. |
I gave up on it. I now have a Raspberry Pi that runs ejabberd, among other things. I have withdrawn my portion of the bounty on this issue. |
Hello,
Would like to report that Ejabberd fails to run after new installation on Synology.
No error msg during installation. However after install, the app attempt to start for 2 minutes after failing with the msg (Failed to run the package service)
System is: DS412+
OS version: DSM 6.0-7321 Update 1
Your help in this matter is appreciated
Thank you.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: