[OpenSIPS-Users] problem starting XCAP server on redhat linux

[GOWDA, Susheela (Susheela)]

Thnx, that helps.

The error says :
=============
/usr/local/lib/python2.6/site-packages/twisted/spread/pb.py:30: DeprecationWarning: the md5 module is deprecated; use hashlib instead
  import md5
/usr/local/lib/python2.6/site-packages/twisted/web2/auth/digest.py:15: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import md5, sha
fatal error: Cannot load 'database' backend module: No module named _mysql_exceptions
============


I have installed SQLObject-0.10.1. My config.ini file is as below, username:test, password:test, Db name:test.

Thanks in advance for any help.
Susheela. 


[Server]

; IP address and port to listen for requests
; 0.0.0.0 means any address of this host
address = 0.0.0.0
port = 443

; The XCAP Root URI; must not contain any port number. If the scheme is
; https, then the server will listen for requests in TLS mode.

; This is a comma/space separated list of XCAP root URIs. The first is the
; primary XCAP root URI, while the others (if specified) are aliases.
; The primary root URI is used when generating xcap-diff

root = https://xcap.example.com/xcap-root

; The backend to be used for storage and authentication. Current supported
; values are Database and OpenSIPS. OpenSIPS backend inherits all the settings
; from the Database backend but performs extra actions related to the
; integration with OpenSIPS for which it read the settings from [OpenSIPS]
; section

backend = Database
;backend = OpenSIPS

; Validate XCAP documents against XML schemas
document_validation = Yes


[Logging]
; directory where to put log files, default is /var/log/openxcap
; if empty, like in the following line, logs will be printed to stdout
;directory=

; The following log_* parameters control what information is logged for
; which errors. Their format is comma-separated list of HTTP error codes
; that should enable the feature currently implemented: log_request_headers,
; log_response_body, log_stacktrace

; Some examples:

; * log stack trace for 500 Internal Error only (default)
;log_stacktrace=500

; * log stack trace (if available) for any error
;log_stacktrace=any

; * log responses sent to the client for 400 and 409 errors (default is 500)
;log_response_body=400,409

; * log headers sent by the client for 401 errors (default is 500)
;log_request_headers=401


[Authentication]

; The HTTP authentication type, this can be either 'basic' or 'digest'.
; If you're using TLS, it's better to choose 'basic' because the data is
; encrypted anyway.
type = basic

; Specify if the passwords are stored as plain text - Yes
; or in a hashed format MD5('username:domain:password') - No
cleartext_passwords = Yes

; The default authentication realm
default_realm = example.com

; A list of trusted peers from where XCAP requests are accepted without HTTP
; authentication e.g. trusted_peers = 10.0.0.0/24, 192.168.0.1
trusted_peers =


[TLS]

; Location of X509 certificate and private key that identify this server.
; The path is relative to /etc/openxcap, or it can be given as an absolute
; path.

; Server X509 certificate
;certificate = tls/server.crt

; Server X509 private key
;private_key = tls/server.key


[Database]

; The database connection URI for the datase with subscriber accounts
authentication_db_uri = mysql://test:test@test/database


; The database connection URI for the database that stores the XCAP documents
storage_db_uri = mysql://test:test@test/database

; Authentication and storage tables
subscriber_table = subscriber
xcap_table = xcap


[OpenSIPS]

; The address and port of the xml-rpc management interface
;xmlrpc_url = http://sip.example.com:8080

; Publish xcap-diff event via OpenSIPS management interface
; enable_publish_xcapdiff = yes








-----Original Message-----
From: users-bounces at lists.opensips.org [mailto:users-bounces at lists.opensips.org] On Behalf Of Sanjeev BA
Sent: Wednesday, October 07, 2009 5:41 PM
To: 'OpenSIPS users mailling list'
Subject: Re: [OpenSIPS-Users] problem starting XCAP server on redhat linux

Try executing with the --no-fork option. It may give you some clue.

Regards
Sanjeev

-----Original Message-----
From: users-bounces at lists.opensips.org [mailto:users-bounces at lists.opensips.org] On Behalf Of Peter Lemenkov
Sent: Wednesday, October 07, 2009 8:58 PM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] problem starting XCAP server on redhat linux

2009/10/7 Susheela <susheelah at alcatel-lucent.com>:
>
> Hi,
> ? I am new to openxcap, have installed Version 1.1.2 on redhat linux 
> box, but having problem while starting the server.
> ?looks like it is failing at "process.daemonize(pidFile)"

There are various possible reasons (perhaps, you'll need superuser's privileges for creating pid-file - just my guess), so I cannot say something valuable here.

However, I advice you to grab srpm-file from there and test it.

https://bugzilla.redhat.com/show_bug.cgi?id=525432

--
With best regards, Peter Lemenkov.

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


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