R: [Serusers] Re:

[Andrey Kouprianov]

Did you set this==>

listen=127.0.0.1

If yes, then it will not work... I dont remember why, but this topic
was already discussed in the list (try searching Google, if you are
interested). If that's the case, then use private IPs to test your SER
(192.168.x.x)

If that's not the case, please, send your ser.cfg attached to the next
email. Let's see what could be the problem.

On 3/15/06, D'Addelfio Davide <Davide.D'Addelfio at italtel.it> wrote:
> I'm trying and trying but still have not success...
>
> I'm working also over cfg file but nothing, he always said me that ser.pid does not exist...what I can do?
>
> Help is needed
> Davide
>
> -----Messaggio originale-----
> Da: serusers-bounces at iptel.org [mailto:serusers-bounces at lists.iptel.org] Per conto di Andrey Kouprianov
> Inviato: mercoledì 15 marzo 2006 10.46
> A: serusers at lists.iptel.org
> Oggetto: [Serusers] Re:
>
> did you say "you can understand"? or still cannot? anyway, it's good,
> if you did find the problem :)
>
> On 3/15/06, D'Addelfio Davide <Davide.D'Addelfio at italtel.it> wrote:
> >
> >
> > this is what i have:
> >
> > [root at serverlinux ser-0.9.4]# tail -n20 /var/log/messages
> > Mar 15 10:12:18 serverlinux ser: Avvio ser succeeded
> > Mar 15 10:12:19 serverlinux crond: Avvio crond succeeded
> > Mar 15 10:12:20 serverlinux xfs: Avvio xfs succeeded
> > Mar 15 10:12:20 serverlinux atd: Avvio atd succeeded
> > Mar 15 10:12:21 serverlinux mdmonitor: mdadm succeeded
> > Mar 15 10:12:21 serverlinux mdmpd: mdmpd succeeded
> > Mar 15 10:12:24 serverlinux kernel: mtrr: your processor doesn't support
> > write-combining
> > Mar 15 10:13:01 serverlinux gdm(pam_unix)[1160]: session opened for user
> > root by (uid=0)
> > Mar 15 10:13:16 serverlinux modprobe: modprobe: Can't locate module
> > sound-slot-0
> > Mar 15 10:13:16 serverlinux modprobe: modprobe: Can't locate module
> > sound-service-0-3
> > Mar 15 10:13:24 serverlinux gconfd (root-1330): Inizializzazione (versione
> > 2.2.1), pid 1330, utente 'root'
> > Mar 15 10:13:25 serverlinux gconfd (root-1330): L'indirizzo
> > "xml:readonly:/etc/gconf/gconf.xml.mandatory" è stato
> > risolta ad una fonte di configurazione in sola lettura in posizione 0
> > Mar 15 10:13:25 serverlinux gconfd (root-1330): L'indirizzo
> > "xml:readwrite:/root/.gconf" è stato risolto ad una fonte di configurazione
> > scrivibile in posizione 1
> > Mar 15 10:13:25 serverlinux gconfd (root-1330): L'indirizzo
> > "xml:readonly:/etc/gconf/gconf.xml.defaults" è stato
> > risolta ad una fonte di configurazione in sola lettura in posizione 2
> > Mar 15 10:16:52 serverlinux modprobe: modprobe: Can't locate module
> > sound-slot-0
> > Mar 15 10:16:52 serverlinux modprobe: modprobe: Can't locate module
> > sound-service-0-3
> > Mar 15 10:19:08 serverlinux ser: WARNING: fix_socket_list: could not rev.
> > resolve 138.132.167.226
> > Mar 15 10:19:08 serverlinux ser: WARNING: fix_socket_list: could not rev.
> > resolve 138.132.167.226
> > Mar 15 10:19:08 serverlinux /usr/local/sbin/ser[1433]: Maxfwd module-
> > initializing
> > Mar 15 10:19:08 serverlinux /usr/local/sbin/ser[1433]: ERROR: tcp_init:
> > bind(7, 0x80fa6bc, 16) on 127.0.0.1: Address already in use
> >
> > i really can understand where is the problem!
>
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>