Topic: Software error: Couldn't open meetme.conf

[gjverheij]

Hi there,

I am a new user of Sail, at the first set up an error, do any one know how the solve this?

a new SME 7.3 box with SAIL 2.2.1-594


The error at the trunklines:
Modify a Trunk or Gateway

NOTE: asterisk is not running. If it does not start after saving a setting something is wrong...

Trunk Definitions

Software error:

Couldn't open meetme.conf  - ending

For help, please send mail to the webmaster (admin), giving this error message and the time and date of the error.


It isn't possible to edit or to delete the trunkline

With regards,

Gert-Jan Verheij

[SARK devs]

did you run console-save after the install?

if not, try running a commit (from any panel).  Then try you change again.

Best

S

[gjverheij]

hi,

Thanks for reaction

I have tried any a commit button (color was red, now blue), but no changes in the error

with regard, Gert-Jan

[SARK devs]

Which rpms did you install?

S

[sonoracomm]

I have updated a couple of SAIL/ SARK installations lately and I have seen some errors pertaining to permissions.

I suspect the problems have to do with startup.

As I understand it, the new 2.2 series is started and restarted like this:

service sark start
or
service sark restart

I have seen where there were apparent leftovers in /etc/rc7.d:

S93asterisk
S93qos
S93tftp
S94fop
plus the newer
S93sark

I think you only need the S93sark link, but I'm not sure...maybe Jeff can clear this up for me?

I suspect that upon startup, the old (leftover from an upgrade) links cause SAIL/Asterisk not to start up properly?

In any event, try restarting SARK and see.

G

[SARK devs]

Hi G

You know this stuff better than we do!

You are quite correct.  The one which will kill you is starting or stopping asterisk (instead of sark).  I think we've gotten rid of most of the hangover bugs in 597/598 but it's in cases where you run 1.2 asterisk and 2.2 sail where we get little niggles.  If in doubt, do this...

config setprop asterisk status disabled

That will ensure that the asterisk daemon doesn't get auto started at system initialization.

Best

S

[sonoracomm]

Thanks much for the info.

Can you please comment on these links:

S93qos
S93tftp
S94fop

Are these services obsolete or taken care of by the S93sark link?

G

[SARK devs]

qos is dead and can be removed.

The other two are still alive and control the start-up of the Flash Operator Panel and the TFTP server

Kind Regards

S

[sonoracomm]

Thanks again.

For me that meant running these commands:

config setprop asterisk status disabled
rm -rf /etc/rc7.d/S93asterisk
rm -rf /etc/rc7.d/S93qos

Then I did:

service sark restart

I suspect I had these leftovers from running SARK 2.1 then upgrading to 2.2.

G

[gjverheij]

Hello again,

First your question S, which rpm did you install?

sail-2.2.1-594.noarch.rpm

but I didn't mention about the sme 7.3 box, it is an epia via board (http://www.via.com.tw/en/products/mainboards/motherboards.jsp?motherboard_id=21). So I have an i586 install (not i686!) of sme.

I have tried the suggestions in this tread, in my believing not for the problem above.

So the problem is there...

Do any one have suggestions?

Greetings Gert-Jan

[SARK devs]

How did you install asterisk?

[gjverheij]

not.... thats the problem, but so I mention i586 versus i686


 rpm -Uvh smeserver-asterisk-zappri-MPP-1.4.4-2.i686.rpm
Preparing...                ########################################### [100%]
        package smeserver-asterisk-zappri-MPP-1.4.4-2 is intended for a i686 architecture

Is there an i586 version avaible?

Greetings Gert-Jan

[SARK devs]

Is there an i586 version avaible?

Not from us I'm afraid.  You may be able to install from ATrpms, I'm not sure if they produce a 386/586 set of rpms.

Failing that you'll need to compile it yourself.  It isn't hard, there are lots of instructional sites out there which will tell you what you need and what you need to do. 

KInd Regards

S