Start and imediatly stop Exiting!
Brought to you by:
jackkane
Menu
▾
▴
#8 Start and imediatly stop Exiting!
closed-fixed
5
2014-01-18
2013-12-06
No
I'm happy yo find this software. But not work for me.
i'm sorry to post her but i'm not find informations about my problem.
My problem.
Environment OS Ubuntu 12.04 Lts 64 bits Kernel 3.2.0-56 SMP
myconf.cfg
[general]
logfile = /home/fred/work/hl7/socket/socketReader.log
loglvl = debug
useconnections = incoming_file
[incoming_file]
queuename = file-to-socket
transtech = file
transdir = in
usehl7 = False
messagedir = /home/fred/work/txt/
filemask = *.dat
cycletime = 10
maxfiles = 5
newline = False
command: /socketReader64 --configfile myconf.cfg
When i start this command, socketreader64 stop imedialty by message Exiting!
when i configure only socket incoming, the probem is identic.
the log in debug mod
2013-12-06 17:57:06,795 - Main - CRITICAL - socketReader 1.2.3 is starting up.
2013-12-06 17:57:06,795 - Main - CRITICAL - Python Interpreter: CPython 2.7.5 64bit
2013-12-06 17:57:06,795 - Main - CRITICAL - Host System: Linux fred-e6530 3.2.0-56-generic #86-Ubuntu SMP Wed Oct 23 09:20:45 UTC 2013 x86_64 x86_64
2013-12-06 17:57:06,796 - Main - CRITICAL - Command: ./socketReader64 --configfile myconf.cfg
2013-12-06 17:57:06,796 - Main - ERROR - socketReader encountered an unexpected exception:
Traceback (most recent call last):
File "<string>", line 377, in <module>
File "<string>", line 310, in startAll
File "<string>", line 205, in spawnThreads
AttributeError: 'NoneType' object has no attribute 'get'</string></string></module></string>
Thank you.
Hi Frederic,
thank you for your bug report. You discovered a real bug here - I'll go into details later. First, I'd like to explain how you need to configure socketReader.
As socketReader is designed to pass messages from one or multiple sources to one or multiple targets, there must at least exist one source and one target for socketReader to start working. According to your config, you just provided the source part. Here is a minimal configuration, taking messages from a socket and writing them to files on a local disk drive.
[general]
logfile = /path/to/socketReader.log
loglvl = warning
useconnections = incoming_socket, outgoing_file
[incoming_socket]
queuename = socket-to-file
transtech = socket
transdir = in
usehl7 = True
useack = True
createserversocket = True
ipaddr = localhost
port = 12345
[outgoing_file]
queuename = socket-to-file
transtech = file
transdir = out
usehl7 = True
messagedir = /path/to/file/storage/
prefix = ""
hl7prefix = True
suffix = .hl7
newline = False
The bug you triggered manifested as socketReader wants to boot at least one thread of both, incoming and outgoing connectors. In your config, you just defined one single connector. It didn't came to me that somebody would ever try this. Therefore, this case is yet unhandled. I will add some sanity checks to the config file parser and a verbose help message.
Best regards,
Sebastian
I't work.
I'm sorry to respond late. Thank you for the software and the reactivity.
Le 06/12/2013 22:17, Sebastian Weigmann a écrit :
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-1"> <title></title> <meta name="GENERATOR" content="LibreOffice 3.3 (Linux)"> <meta name="AUTHOR" content="Fred "> <meta name="CREATED" content="20111230;17470100"> <meta name="CHANGEDBY" content="Fred "> <meta name="CHANGED" content="20111230;18040200"> <style type="text/css"> <!-- @page { margin: 2cm } P { margin-bottom: 0.21cm } A:link { so-language: zxx } --> </style>
. Pgp key : http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x34D79EDCBA0EB352
Related
Bugs:
#8Fixed with SVN trunk revision 203. This fix will be included in release 1.2.4.
A check has been implemented to prevent startup if there is no input or no output connection defined for a queue. The user will be prompted to check the config file.