Jump to content

Problems upgrading to 5.2 on Mac Mini


chidcp1
 Share

Recommended Posts

Hi,

 

Tried to update from 5.1.3 to 5.2 the other day and hit similar problems to others have reported, but managed to reinstall back to 5.1.3.

 

Saw you said there had been problems and that you had rebuilt the upgrades, so I've just tried again and still get problems! This is running on a Mac Mini under Mavericks Server.

 

After entering the upgrade xml address, it says that it has been successfully updated so I unload/load Snomone to restart it.

 

I cannot gain access to the web interface and looking at the Snomone console log, I see

 

Starting up
[0] 20140227152717: Upgrading from 1.x to 2.0
[0] 20140227152718: HTTP: Port number 0 is invalid, taking 80 instead
[0] 20140227152718: TCP(IPv4): Could not bind socket to port 80 on IP 0.0.0.0
[0] 20140227152718: Could not open TCP port 80
[0] 20140227152718: HTTP: Port number 0 is invalid, taking 80 instead
[0] 20140227152718: TCP(IPv6): Could not bind socket to port 80 on IP [::]
[0] 20140227152718: Could not open TCP port 80
[0] 20140227152718: TFTP: Port number 0 is invalid, taking 69 instead
[0] 20140227152718: Last message repeated 2 times
[0] 20140227152718: TCP(IPv4): Could not bind socket to port 5060 on IP 0.0.0.0
[0] 20140227152718: Could not open TCP port 5060 for SIP
[0] 20140227152718: TCP(IPv6): Could not bind socket to port 5060 on IP [::]
[0] 20140227152718: Could not open TCP port 5060 for SIP
[0] 20140227152918: HTTP: Port number 0 is invalid, taking 80 instead
[0] 20140227152918: TCP(IPv4): Could not bind socket to port 80 on IP 0.0.0.0
[0] 20140227152918: Could not open TCP port 80
[0] 20140227152918: HTTP: Port number 0 is invalid, taking 80 instead
[0] 20140227152918: TCP(IPv6): Could not bind socket to port 80 on IP [::]
[0] 20140227152918: Could not open TCP port 80
[0] 20140227152918: TCP(IPv4): Could not bind socket to port 5060 on IP 0.0.0.0
[0] 20140227152918: Could not open TCP port 5060 for SIP
[0] 20140227152918: TCP(IPv6): Could not bind socket to port 5060 on IP [::]
[0] 20140227152918: Could not open TCP port 5060 for SIP

 

 

It does not appear to be taking any notice of the specified ports in the configuration pbx.xml file?

 

I've yet again had to reinstall/upgrade back to 5.1.3. After reinstalling 5.1, it reads the correct ports etc from pbx.xml.

 

Please advise if there is still a problem with the Mac OSX upgrade, or let me know if you need more details.

 

Thanks

 

 

Link to comment
Share on other sites

Well regarding the ports, it might take a minute before it can finally (exclusively) bind to the ports 80 etc. I would not be worried about that. Just double check that you don't have tow PBX processes running at the same time.

 

But it seems that your PBX configuration got wiped out somehow before the new image started up. File system full?

Link to comment
Share on other sites

Hi, there is nothing obviously wrong. Snomone is configured to use ports 81 and 444. When I upgrade to 5.2 and get the port error messages, I can still see pbx.xml contains ports 81 and 444, but the 3.2 version is not taking any notice of pbm.xml. As soon as I go back to 3.1.1/3 it correctly uses ports 81/444, without me having to touch pbx.xml or reset anything.

 

I really think there is an issue with 3.2 for Mac failing to take any notice of pbx.xml at startup?

 

Please let me know if you need any other details.

Thanks

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...