Custom Query (104 matches)
Results (40 - 42 of 104)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #109 | worksforme | Sometimes the systemctl command gets stuck when stopping ntripcaster service | ||
| Description |
I have installed the professional ntripcaster release 2.0.31 on an AWS EC2 server instance running Ubuntu 18.04 I followed the readme and added the ntripcaster scripts/ntripcaster.service file to /etc/systemd/system It works fine most of the time and the service always starts fine after a system reboot. However sometimes after I have edited the configuration files in /usr/local/ntripcaster/config I find the "systemctl restart ntripcaster.service" command hangs. If I check the systemctl status it says the ntripcaster service is stuck in the stopping state with no logs to indicate the issue. If I do a "systemctl stop ntripcaster.service" then "systemctl start ntripcaster.service" the chance of it getting stuck is lower but it does still happen occasionally. To fix the stuck state I end up rebooting the server and everything then starts up again without issue. I don't think I have had this command get stuck if I haven't modified the config files, but can't be 100% certain. It should be fairly easy to recreate this as my config is rather basic with only a handful of mountpoints, users and groups. I haven't changed anything in ntripcaster.conf except for the host name, and basic contact details. P.S. the version dropdown below didn't have 2.0.31 so I just selected another version. |
|||
| #108 | wontfix | Add monitoring functionalities for BNC | ||
| Description |
If scanRTCM enabled:
|
|||
| #106 | fixed | BNC Client v 2.12.6 latency metrics stop recording in the log at beginning of UTC week | ||
| Description |
Hello, We are running the BNC Client to collect latency metrics and create 1s Rinex2 files from our streaming stations across New Zealand. We manage about 50 streaming sites with one instance of the BNC client. We have upgraded to the latest BNC version (2.12.6) last week on 2018/05/16. BNC Client stopped logging metrics at the beginning of the midnight of UTC day 2018- 05-20. The latency records restarted normally after a restart of the BNC Client. I have enclosed the configuration file we use with the BNC Client (only username and password are changed in there) and the BNC log file for the day that had the latency metrics dropping off. We run BNC Client on: Linux 3.10.0-862.2.3.el7.x86_64 x86_64 x86_64 x86_64 GNU/Linux with the following command: /usr/local/bin/bnc -nw --conf /work/bnc/conf/BNC.ini I know that our colleagues at Geoscience Australia are having the same problem, and they experienced the same behavior at the beginning of each UTC week. We were previously using v 2.12.3 of the software with no issues. Thanks a lot for your attention, Kind regards, Elisabetta --- Elisabetta D’Anastasio Geodetic Processing Specialist Geohazards Monitoring Department, GNS Science - Te Pῡ Ao |
|||
