[OpenSIPS-Users] FW: Error starting opensips 1.8.1

Fri Aug 31 16:45:48 CEST 2012

Hi Odin
Could you please explain how to add modules (or load modules in Opensips)
Please describe .

Regards
Shimon
________________________________________
From: users-bounces at lists.opensips.org [users-bounces at lists.opensips.org] on behalf of Odin Gremaud [odin.gremaud at nexcom.fr]
Sent: Thursday, August 30, 2012 6:43 PM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Error starting opensips 1.8.1

Hi,

You should add the 'sipmsgops' module to use the 'is_method' function. The
function was originally in the 'textops' module, which was split into
'textops' and 'sipmsgops'. This should solve your issue.

Hope this helps.

Regards,

Odin

On Thu, 30 Aug 2012 17:35:28 +0200, Shimon Mishal
<shimon.mishal at telrad.com> wrote:

>
> Hi list,
>
> I've just install the 1.8.1 version.
> But I get the following:
> Could you please advise?
>
>
> 1.  [ec2-user at ip-10-128-35-32 opensips-1.8.1-tls]$ opensipsctl start
>
> INFO: Starting OpenSIPS :
>
> ERROR: PID file /var/run/opensips.pid does not exist -- OpenSIPS start
> failed
> [ec2-user at ip-10-128-35-32 opensips-1.8.1-tls]$ sudo tail
> /var/log/messages
> Aug 30 14:49:48 ip-10-128-35-32 opensips: CRITICAL:core:yyerror: parse
> error in config file, line 193, column 18-19: unknown command
> <is_method>, missing loadmodule?
> Aug 30 14:49:48 ip-10-128-35-32 opensips: CRITICAL:core:yyerror: parse
> error in config file, line 202, column 21-22: unknown command
> <is_method>, missing loadmodule?
> Aug 30 14:49:48 ip-10-128-35-32 opensips: CRITICAL:core:yyerror: parse
> error in config file, line 223, column 20-21: unknown command
> <is_method>, missing loadmodule?
> Aug 30 14:49:48 ip-10-128-35-32 opensips: CRITICAL:core:yyerror: parse
> error in config file, line 229, column 19-20: unknown command
> <is_method>, missing loadmodule?
> Aug 30 14:49:48 ip-10-128-35-32 opensips: CRITICAL:core:yyerror: parse
> error in config file, line 233, column 18-19: unknown command
> <is_method>, missing loadmodule?
> Aug 30 14:49:48 ip-10-128-35-32 opensips: CRITICAL:core:yyerror: parse
> error in config file, line 240, column 19-20: unknown command
> <append_hf>, missing loadmodule?
> Aug 30 14:49:48 ip-10-128-35-32 opensips: CRITICAL:core:yyerror: parse
> error in config file, line 247, column 18-19: unknown command
> <is_method>, missing loadmodule?
> Aug 30 14:49:48 ip-10-128-35-32 opensips: CRITICAL:core:yyerror: parse
> error in config file, line 253, column 18-19: unknown command
> <is_method>, missing loadmodule?
> Aug 30 14:49:48 ip-10-128-35-32 opensips: CRITICAL:core:yyerror: parse
> error in config file, line 296, column 18-19: unknown command
> <is_method>, missing loadmodule?
> Aug 30 14:49:48 ip-10-128-35-32 opensips: ERROR:core:main: bad config
> file (14 errors)
> [ec2-user at ip-10-128-35-32 opensips-1.8.1-tls]$
> ----------------------------------------------------------------------------------------------
>
> 2.     [ec2-user at ip-10-128-35-32 opensips-1.8.1-tls]$ sudo opensipsdbctl
> create
> ERROR: database engine not specified, please setup one in the config
> script
>
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 3.[ec2-user at ip-10-128-35-32 opensips-1.8.1-tls]$ cat
> /etc/default/opensips
> #
> # OpenSIPS startup options
> #
>
> # Set to yes to enable opensips, once configured properly.
> RUN_OPENSIPS=yes
>
> # User to run as
> USER=opensips
>
> # Group to run as
> GROUP=opensips
>
> # Amount of memory to allocate for the running OpenSIPS server (in Mb)
> MEMORY=128
>
> # Enable the server to leave a core file when it crashes.
> # Set this to 'yes' to enable OpenSIPS to leave a core file when it
> crashes
> # or 'no' to disable this feature. This option is case sensitive and only
> # accepts 'yes' and 'no' and only in lowercase letters.
> # On some systems (e.g. Ubuntu 6.10, Debian 4.0) it is necessary to
> specify
> # a directory for the core files to get a dump. Look into the opensips
> # init file for an example configuration.
> DUMP_CORE=no
> [ec2-user at ip-10-128-35-32 opensips-1.8.1-tls]$
>
>
>
>
>
> ************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals &
> computer viruses.
> ************************************************************************************
>
>

_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************

_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************