pxReceiver crashes when routing file missing.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
It doesn't give an error message,..
It prints:
2016-11-06 15:48:01,071 [INFO] Receiver file has been started
2016-11-06 15:48:01,072 [INFO] Initialisation of source file
2016-11-06 15:48:01,072 [INFO] Ingestor (source file) can link files to clients: ['file']
2016-11-06 15:48:01,073 [INFO] Initialisation of client file
2016-11-06 15:48:01,091 [INFO] Routing table used: /etc/px/pxRouting.conf
2016-11-06 15:48:11,665 [INFO] Receiver file has been started
and then crashes. ps ax shows no receiver running, but there is no error message complaining about the missing routing file. It should complain more obviously.
Was: https://sourceforge.net/p/metpx/bugs/58/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing pxReceiver with /etc/px/pxRouting.conf absent, then trace the receiver startup path and routing-table initialization to find where the process exits without reporting the missing file. Done means the missing routing file produces an explicit, visible error instead of a silent crash; no source file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100