MMSC locked from error msg

MMSC locked from error msg SearchSearch
Author Message
Brian Snyder
New member
Username: Bsnyder

Post Number: 7
Registered: 11-2010
Posted on Wednesday, December 08, 2010 - 12:54 am:   

I've tried rebooting, restarting the services, everything... My next step is re-instally if you guys can't tell me what I have setup wrong..

I'm attaching screenshots of every one of the configurations relevant to the MMSC, I just can't figure out why its throwing an error to a route that doesn't existing anymore...
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2700
Registered: 08-2008
Posted on Wednesday, December 08, 2010 - 01:02 am:   

If the route was deleted, it may be a "ghost" error that is not actually causing operational problem. Look for any *.ERR files in the NowSMS data directory. Delete them. If there is a real problem, they will reappear.
Brian Snyder
New member
Username: Bsnyder

Post Number: 8
Registered: 11-2010
Posted on Wednesday, December 08, 2010 - 08:08 pm:   

I corrected the ghost error, however, when I try to send any type of MMS message it gives me:

Error: Internal Error:

SMS is functioning properly, and I haven't changed anything for the MMSC. The previous error msg (the ghost error) has disapeared. }
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2707
Registered: 08-2008
Posted on Wednesday, December 08, 2010 - 09:10 pm:   

No information after Internal error?

Usually it will be an issue that the MMSC service is not running due to a po rt conflict.

The SMS service manages the web interface, but it makes a TCP connection to t he MMSC service when it needs to send an MMS.

Historically, there has been an issue that the MMSC service will not start i f it cannot bind to the HTTP or SMTP port specified in the MMSC configuratio n, even if you have no intent of using SMTP. So you may wish to change the S MTP port setting.

If this does not resolve the problem, the SMSDEBUG.LOG would tell us more.

-- Des (NowSMS Support)
Brian Snyder
New member
Username: Bsnyder

Post Number: 9
Registered: 11-2010
Posted on Wednesday, December 08, 2010 - 10:42 pm:   

yeah it was a very non specific error. The port issue should not have been an issue...

Both the default ports 8080 and port 25 (smtp) are available on the system. I'm not sure exactly what is causing the conflict. I looked through the SMS debug.log and found nothing that stuck out.

A re-install of the software seemed to work fine (restored all settings back to normal)

Strange bug, but resolved by re-installing
Brian Snyder
New member
Username: Bsnyder

Post Number: 11
Registered: 11-2010
Posted on Thursday, December 09, 2010 - 12:29 am:   

Ok Scratch that. I'm getting the same error again. Now in regards to you saying it won't start if it cannot bind to the http or smtp port... Where in the MMSC configuration specified at to make sure this isn't an issue?

I've tried changing and using a varierty of ports 8080, 9001, etc, but cannot get the MMSC to function properly... I currently have the firewall completly disabled, so it shouldn't be a conflict...

IN addition since the re-isntall, it hasn't generated an SMSDEBUG.LOG...

Really stuck now, don't think I made any major / fundamental changes to the system setup either...

Thanks for you help.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2711
Registered: 08-2008
Posted on Thursday, December 09, 2010 - 12:48 am:   

Enable the SMSDEBUG.LOG and MMSCDEBUG.LOG ... checkboxes are hidden on the "Serial #" page.

Also change that "IP Address" setting drop down box on the MMSC page to the "(all available)" choice. If you're on a dynamic IP of some sort, this setting could be causing the problem.
Brian Snyder
New member
Username: Bsnyder

Post Number: 12
Registered: 11-2010
Posted on Thursday, December 09, 2010 - 12:57 am:   

ahhh.. The debug logs were disabled after the re-install... Forgot to enable again.

I have a static IP, and have that selected, but went ahead and changed it to all available... Still haveing issues. I ran a netstat -a and it appears I have about 3-4 entries on port 8080 that might be causing a conflict... Is there any reason I have to stick with 8080 or can I change the port to anything I want?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2712
Registered: 08-2008
Posted on Thursday, December 09, 2010 - 01:03 am:   

The port number is flexible. In your case only the SMS service is using it to communicate with the MMS service.

The only problem I can recall similar to what you describe was one where an internal IP network address conflicted with the dynamic IP Range that got assigned by the operator for GPRS connections. I don't think that would be an issue for your config. I also believe the (all available) setting would prevent that issue from interrupting this type of communication.

I am going off line until tomorrow. Hopefully debug logs will provide a clue.
Brian Snyder
New member
Username: Bsnyder

Post Number: 13
Registered: 11-2010
Posted on Thursday, December 09, 2010 - 01:08 am:   

thanks for all the help, it looks like it was a port conflict... MMSC is back up and running now. Now to tackle the SMIL issues

Thanks for all your help