Sep 29 19:44:11 dns ser: WARNING: fix_socket_list: could not rev. resolve 192.168.0.254 Sep 29 19:44:11 dns ser: WARNING: fix_socket_list: could not rev. resolve 192.168.0.254 Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: Maxfwd module- initializing Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: new_connection(): Access denied for user: 'serro@localhost' (Using password: YES) Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: db_init(): Could not create a connection Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: ERROR: auth_db_ver: unable to open database connection Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: auth_db:str_fixup(): Error while querying table version Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: ERROR: fix_expr : fix_actions error
Q: 1. Where do the Warning 192.168.0.254 come from? My network does not use 192.168.0.x
2. Access denied is most likely the error for all following errors. Note the quote marks, they are around the entire name and not 'serro'@'localhost' I am not sure if that makes a difference. The access to the database is for me not clear in the moment. We have a user ser with password serpassword and a user serro with password serropassword. We have also admin with the password adminpassword. I don't find the user/passwords in the config files.
My ser.cfg looks like that: grep -v ^[$,#] ser.cfg
/* Uncomment these lines to enter debugging mode fork=no log_stderror=yes */
check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) fifo="/tmp/ser_fifo"
loadmodule "/usr/local/lib/ser/modules/mysql.so"
loadmodule "/usr/local/lib/ser/modules/sl.so" loadmodule "/usr/local/lib/ser/modules/tm.so" loadmodule "/usr/local/lib/ser/modules/rr.so" loadmodule "/usr/local/lib/ser/modules/maxfwd.so" loadmodule "/usr/local/lib/ser/modules/usrloc.so" loadmodule "/usr/local/lib/ser/modules/registrar.so" loadmodule "/usr/local/lib/ser/modules/textops.so"
loadmodule "/usr/local/lib/ser/modules/auth.so" loadmodule "/usr/local/lib/ser/modules/auth_db.so"
modparam("usrloc", "db_mode", 2)
modparam("usrloc", "db_url", "mysql://ser:serpassword@localhost/ser") modparam("auth", "secret", "myphrase")
modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "password_column", "password")
modparam("rr", "enable_full_lr", 1)
route{
# initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); break; };
# we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route();
# subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); break; };
if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); route(1); break; };
# if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==trace-intl.net) {
if (method=="REGISTER") {
if (!www_authorize("trace-intl.net", "subscriber")) { www_challenge("trace-intl.net", "0"); break; };
save("location"); break; };
lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); break; };
# native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; append_hf("P-hint: usrloc applied\r\n"); route(1); }
route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; }
On 29-09-2005 21:25, Ronald Wiplinger wrote:
Sep 29 19:44:11 dns ser: WARNING: fix_socket_list: could not rev. resolve 192.168.0.254 Sep 29 19:44:11 dns ser: WARNING: fix_socket_list: could not rev. resolve 192.168.0.254 Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: Maxfwd module- initializing Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: new_connection(): Access denied for user: 'serro@localhost' (Using password: YES) Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: db_init(): Could not create a connection Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: ERROR: auth_db_ver: unable to open database connection Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: auth_db:str_fixup(): Error while querying table version Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: ERROR: fix_expr : fix_actions error
Q:
- Where do the Warning 192.168.0.254 come from? My network does not use
192.168.0.x
It is either configured in the configuration file using listen directive, or one of your network interfaces has this address, or the domain name SER is configured with resolves to the IP address.
- Access denied is most likely the error for all following errors. Note
the quote marks, they are around the entire name and not 'serro'@'localhost' I am not sure if that makes a difference. The access to the database is for me not clear in the moment. We have a user ser with password serpassword and a user serro with password serropassword. We have also admin with the password adminpassword. I don't find the user/passwords in the config files.
In mysql you also need to specify the hostname, that is, serro@a is different than serro@localhost, ser_mysql.sh uses the following statements to create users:
# Users: ser is the regular user, serro only for reading GRANT ALL PRIVILEGES ON $1.* TO $USERNAME IDENTIFIED BY '$DEFAULT_PW'; GRANT ALL PRIVILEGES ON $1.* TO ${USERNAME}@$DBHOST IDENTIFIED BY '$DEFAULT_PW'; GRANT SELECT ON $1.* TO $ROUSER IDENTIFIED BY '$RO_PW'; GRANT SELECT ON $1.* TO ${ROUSER}@$DBHOST IDENTIFIED BY '$RO_PW';
where $USERNAME, $DEFAULT_PW, $DBHOST, $ROUSER, $RO_PW are variables that will be expanded. In this case ROUSER will be replaced with serro and DBHOST will be replaced with localhost.
Jan.
Ronald Wiplinger wrote:
Sep 29 19:44:11 dns ser: WARNING: fix_socket_list: could not rev. resolve 192.168.0.254 Sep 29 19:44:11 dns ser: WARNING: fix_socket_list: could not rev. resolve 192.168.0.254 Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: Maxfwd module- initializing Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: new_connection(): Access denied for user: 'serro@localhost' (Using password: YES) Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: db_init(): Could not create a connection Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: ERROR: auth_db_ver: unable to open database connection Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: auth_db:str_fixup(): Error while querying table version Sep 29 19:44:11 dns /usr/local/sbin/ser[19346]: ERROR: fix_expr : fix_actions error
Q:
- Where do the Warning 192.168.0.254 come from? My network does not
use 192.168.0.x
This one I could solve. I have a four port Ethernet card in that machine, with that network on eth2, ...
However, for the rest I did not come a bit closer. Can anybody give me a hint, please? I am sure it is in the config file below, but I do not know where.
bye
Ronald Wiplinger
- Access denied is most likely the error for all following errors.
Note the quote marks, they are around the entire name and not 'serro'@'localhost' I am not sure if that makes a difference. The access to the database is for me not clear in the moment. We have a user ser with password serpassword and a user serro with password serropassword. We have also admin with the password adminpassword. I don't find the user/passwords in the config files.
My ser.cfg looks like that: grep -v ^[$,#] ser.cfg
/* Uncomment these lines to enter debugging mode fork=no log_stderror=yes */
check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) fifo="/tmp/ser_fifo"
loadmodule "/usr/local/lib/ser/modules/mysql.so"
loadmodule "/usr/local/lib/ser/modules/sl.so" loadmodule "/usr/local/lib/ser/modules/tm.so" loadmodule "/usr/local/lib/ser/modules/rr.so" loadmodule "/usr/local/lib/ser/modules/maxfwd.so" loadmodule "/usr/local/lib/ser/modules/usrloc.so" loadmodule "/usr/local/lib/ser/modules/registrar.so" loadmodule "/usr/local/lib/ser/modules/textops.so"
loadmodule "/usr/local/lib/ser/modules/auth.so" loadmodule "/usr/local/lib/ser/modules/auth_db.so"
modparam("usrloc", "db_mode", 2)
modparam("usrloc", "db_url", "mysql://ser:serpassword@localhost/ser") modparam("auth", "secret", "myphrase")
modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "password_column", "password")
modparam("rr", "enable_full_lr", 1)
route{
# initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); break; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); break; }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); route(1); break; }; # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==trace-intl.net) { if (method=="REGISTER") { if (!www_authorize("trace-intl.net",
"subscriber")) { www_challenge("trace-intl.net", "0"); break; };
save("location"); break; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); break; }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; append_hf("P-hint: usrloc applied\r\n"); route(1);
}
route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; }