Hylafax Mailing List Archives

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

[hylafax-users] mgetty hangs up the line



First of all, thanks to Vyacheslav Frolov for his help with my class 2 setup.
 
I still have some problems though. From one side, I'm using minicom to dial in to the other computer, having hylafax and mgetty installed. If I set up inittab to run mgetty at bootup instead of faxgetty, I'm given the login prompt, and I can log in. But when faxgetty is running, minicom connects, but immediately writes: NO CARRIER.
The interesting thing (for me at least) is that mgetty (login?) does not recognize that the line was dropped, and blocks hylafax. Looking at ps fx, I can see that there is a login process running, it must be killed explicitly.
 
My understanding is that in hyla's config file, one can specify the arguments, that are turned over to mgetty (symlinked getty-link). Having the same arguments as in inittab (that I tied, and it worked), plus -r so that mgetty does not reset the modem, it still doesn't work.
 
Let me include some of the log:
 
Jan 12 18:10:58 roliboy FaxGetty[428]: STATE CHANGE: RUNNING -> LISTENING
Jan 12 18:10:58 roliboy FaxGetty[428]: MODEM input buffering enabled
Jan 12 18:10:58 roliboy FaxGetty[428]: --> [4:RING]
Jan 12 18:11:00 roliboy FaxGetty[428]: --> [4:RING]
Jan 12 18:11:00 roliboy FaxGetty[428]: STATE CHANGE: LISTENING -> ANSWERING
Jan 12 18:11:00 roliboy FaxGetty[428]: MODEM input buffering enabled
Jan 12 18:11:22 roliboy FaxGetty[428]: ANSWER: DATA CONNECTION
Jan 12 18:11:22 roliboy FaxGetty[428]: GETTY: START "/etc/hylafax/getty-link -x 9 -s 115200 -r ttyS0", pid 429
Jan 12 18:11:50 roliboy FaxGetty[428]: GETTY: exit status 011
 
Exit status 11 is because I killed login manually, I believe.
This is what I got in config.ttyS0:    GettyArgs: "-D -x 9 -s %s -r %l"
 
I'd also like to include mgetty logfile, it might be relavant. Sorry for this long list, but let me point at two things: there are quite a few IO errors in there, and it seems to misidentify the user. Eventually, I'd like to set up ppp instead of shell login, but once shell works, I think I can handle ppp. I also hope, that this error is not a result of mixing shell login and some tries on ppp.
 
Thank you for taking time to answer me.
Roland Szabo
 

--
01/12 18:05:11 yS0  mgetty: experimental test release 1.1.21-Jul24
01/12 18:05:11 yS0   mgetty.c compiled at Aug 31 2000, 19:07:27
01/12 18:05:11 yS0   user id: 0, parent pid: 403
01/12 18:05:11 yS0   reading configuration data for port 'ttyS0'
01/12 18:05:11 yS0   reading /etc/mgetty/mgetty.config...
01/12 18:05:11 yS0   conf lib: read: 'debug 4'
01/12 18:05:11 yS0   conf lib: read: 'fax-id '
01/12 18:05:11 yS0   conf lib: read: 'speed 38400'
01/12 18:05:11 yS0   conf lib: read: 'issue-file /etc/issue.mgetty'
01/12 18:05:11 yS0   key: 'speed', type=0, flags=2, data=115200
01/12 18:05:11 yS0   key: 'switchbd', type=0, flags=1, data=0
01/12 18:05:11 yS0   key: 'direct', type=3, flags=2, data=TRUE
01/12 18:05:11 yS0   key: 'blocking', type=3, flags=1, data=FALSE
01/12 18:05:11 yS0   key: 'port-owner', type=1, flags=1, data=root
01/12 18:05:11 yS0   key: 'port-group', type=1, flags=1, data=dialout
01/12 18:05:11 yS0   key: 'port-mode', type=0, flags=1, data=432
01/12 18:05:11 yS0   key: 'toggle-dtr', type=3, flags=1, data=TRUE
01/12 18:05:11 yS0   key: 'toggle-dtr-waittime', type=0, flags=1, data=500
01/12 18:05:11 yS0   key: 'need-dsr', type=3, flags=1, data=FALSE
01/12 18:05:11 yS0   key: 'data-only', type=3, flags=1, data=FALSE
01/12 18:05:11 yS0   key: 'fax-only', type=3, flags=1, data=FALSE
01/12 18:05:11 yS0   key: 'modem-type', type=1, flags=1, data=auto
01/12 18:05:11 yS0   key: 'modem-quirks', type=0, flags=0, data=(empty)
01/12 18:05:11 yS0   key: 'init-chat', type=2, flags=1, data= \dATQ0V1H0 OK AT OK
01/12 18:05:11 yS0   key: 'force-init-chat', type=2, flags=1, data= \d\d\d\d+++\d\d\d
\dATQ0V1H0 OK
01/12 18:05:11 yS0   key: 'post-init-chat', type=2, flags=0, data=(empty)
01/12 18:05:11 yS0   key: 'data-flow', type=4, flags=1, data=1
01/12 18:05:11 yS0   key: 'fax-send-flow', type=4, flags=1, data=7
01/12 18:05:11 yS0   key: 'fax-rec-flow', type=4, flags=1, data=7
01/12 18:05:11 yS0   key: 'modem-check-time', type=0, flags=1, data=3600
01/12 18:05:11 yS0   key: 'rings', type=0, flags=1, data=1
01/12 18:05:11 yS0   key: 'msn-list', type=2, flags=0, data=(empty)
01/12 18:05:11 yS0   key: 'get-cnd-chat', type=2, flags=0, data=(empty)
01/12 18:05:11 yS0   key: 'cnd-program', type=1, flags=0, data=(empty)
01/12 18:05:11 yS0   key: 'answer-chat', type=2, flags=1, data= ATA CONNECT \c
 
01/12 18:05:11 yS0   key: 'answer-chat-timeout', type=0, flags=1, data=80
01/12 18:05:11 yS0   key: 'autobauding', type=3, flags=1, data=FALSE
01/12 18:05:11 yS0   key: 'ringback', type=3, flags=1, data=FALSE
01/12 18:05:11 yS0   key: 'ringback-time', type=0, flags=1, data=30
01/12 18:05:11 yS0   key: 'ignore-carrier', type=3, flags=1, data=FALSE
01/12 18:05:11 yS0   key: 'issue-file', type=1, flags=3, data=/etc/issue.mgetty
01/12 18:05:11 yS0   key: 'prompt-waittime', type=0, flags=1, data=500
01/12 18:05:11 yS0   key: 'login-prompt', type=1, flags=1, data=@!login:
01/12 18:05:11 yS0   key: 'login-time', type=0, flags=1, data=240
01/12 18:05:11 yS0   key: 'fido-send-emsi', type=3, flags=1, data=TRUE
01/12 18:05:11 yS0   key: 'login-conf-file', type=1, flags=1, data=login.config
01/12 18:05:11 yS0   key: 'fax-id', type=1, flags=3, data=
01/12 18:05:11 yS0   key: 'fax-min-speed', type=0, flags=1, data=0
01/12 18:05:11 yS0   key: 'fax-max-speed', type=0, flags=1, data=14400
01/12 18:05:11 yS0   key: 'fax-server-file', type=1, flags=0, data=(empty)
01/12 18:05:11 yS0   key: 'diskspace', type=0, flags=1, data=1024
01/12 18:05:11 yS0   key: 'notify', type=1, flags=1, data=root
01/12 18:05:11 yS0   key: 'fax-owner', type=1, flags=1, data=root
01/12 18:05:11 yS0   key: 'fax-group', type=1, flags=1, data=fax
01/12 18:05:11 yS0   key: 'fax-mode', type=0, flags=1, data=432
01/12 18:05:11 yS0   key: 'debug', type=0, flags=2, data=9
01/12 18:05:11 yS0   key: 'statistics-chat', type=2, flags=0, data=(empty)
01/12 18:05:11 yS0   key: 'statistics-file', type=1, flags=0, data=(empty)
01/12 18:05:11 yS0   key: 'gettydefs', type=1, flags=1, data=n
01/12 18:05:11 yS0   key: 'term', type=1, flags=0, data=(empty)
01/12 18:05:11 yS0  check for lockfiles
01/12 18:05:11 yS0  huh? It's *our* lock file!
01/12 18:05:11 yS0  locking the line
01/12 18:05:11 yS0   makelock(ttyS0) called
01/12 18:05:11 yS0   do_makelock: lock='/var/lock/LCK..ttyS0'
01/12 18:05:11 yS0  we *have* the line!
01/12 18:05:11 yS0   lock made
01/12 18:05:12 yS0   tio_get_rs232_lines: status: RTS CTS DSR DTR DCD
01/12 18:05:12 yS0  WARNING: DCD line still active, check modem settings (AT&Dx)
01/12 18:05:12 yS0  lowering DTR to reset Modem
01/12 18:05:12 yS0  TIOCMBIS failed: Input/output error
01/12 18:05:12 yS0  cannot turn off soft carrier: Input/output error
01/12 18:05:12 yS0  tcgetattr failed: Input/output error
01/12 18:05:12 yS0  cannot get TIO: Input/output error
01/12 18:05:12 yS0  mg_init_device failed, trying again
01/12 18:05:12 yS0   tio_get_rs232_lines: status: RTS CTS DSR DTR
01/12 18:05:12 yS0  lowering DTR to reset Modem
01/12 18:05:13 yS0   tss: set speed to 115200 (10002)
01/12 18:05:13 yS0   tio_set_flow_control( HARD )
01/12 18:05:13 yS0   waiting for line to clear (VTIME), read:
01/12 18:05:13 yS0   waiting for line to clear (VTIME), read:
01/12 18:05:13 yS0   removing lock file
01/12 18:05:13 yS0  waiting...
01/12 18:05:14 yS0    select returned 1
01/12 18:05:14 yS0   checking lockfiles, locking the line
01/12 18:05:14 yS0   makelock(ttyS0) called
01/12 18:05:14 yS0   do_makelock: lock='/var/lock/LCK..ttyS0'
01/12 18:05:14 yS0   lock made
01/12 18:05:14 yS0   waiting for line to clear (VTIME), read: [0d][0a]OK[0d][0a]
01/12 18:05:14 yS0    looking for utmp entry... (my PID: 406)
01/12 18:05:14 yS0   utmp + wtmp entry made
01/12 18:05:15 yS0   tio_set_flow_control( HARD )
01/12 18:05:15 yS0   print welcome banner (/etc/issue.mgetty)
01/12 18:05:15 yS0   getlogname (FIDO AUTO_PPP), read:[0d]
01/12 18:05:15 yS0   input finished with '\r', setting ICRNL ONLCR
01/12 18:05:15 yS0   tio_set_flow_control( HARD )
01/12 18:05:15 yS0   print welcome banner (/etc/issue.mgetty)
01/12 18:05:15 yS0   getlogname (FIDO AUTO_PPP), read:[0d]
01/12 18:05:15 yS0   input finished with '\r', setting ICRNL ONLCR
01/12 18:05:15 yS0   tio_set_flow_control( HARD )
01/12 18:05:15 yS0   print welcome banner (/etc/issue.mgetty)
01/12 18:05:15 yS0   getlogname (FIDO AUTO_PPP), read: ttyS0 115200 (DIRECT)[0a]
01/12 18:05:15 yS0   tio_get_rs232_lines: status: RTS CTS DSR DTR
01/12 18:05:15 yS0  WARNING: starting login while DCD is low!
01/12 18:05:15 yS0    login: use login config file /etc/mgetty/login.config
01/12 18:05:15 yS0   match: user='ttyS0 115200 (DIRECT)', key=''
01/12 18:05:15 yS0   match: user='ttyS0 115200 (DIRECT)', key=''
01/12 18:05:15 yS0   match: user='ttyS0 115200 (DIRECT)', key='/AutoPPP/'
01/12 18:05:15 yS0   match: user='ttyS0 115200 (DIRECT)', key=''
01/12 18:05:15 yS0   match: user='ttyS0 115200 (DIRECT)', key='*'*** hit!
01/12 18:05:15 yS0   calling login: cmd='/bin/login', argv[]='login ttyS0 115200 (DIRECT)'
01/12 18:05:15 ##### data dev=ttyS0, pid=406, caller='none', conn='DIRECT', name='', cmd='/bin/login', user='ttyS0 115200 (DIRECT)'
01/12 18:05:15 yS0   setenv: 'CALLER_ID=none'
01/12 18:05:15 yS0   setenv: 'CALLED_ID='
01/12 18:05:15 yS0   setenv: 'CONNECT=DIRECT'


Home
Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services