×

INDI Library v1.9.0 Released (23 Apr 2021)

Major INDI Library release v1.9.0 bring significant internal changes championed by @pawel-soja to modernize core INDI Library drivers and clients. New drivers for DeepSkyDad Flat Panel & Pegasus devices plus further improvements to PCM8 drivers.

Weather radio don't want connect

  • Posts: 173
  • Thank you received: 3
duplicate of the previous message
Last edit: 4 months 3 weeks ago by Porchet.
4 months 3 weeks ago #66323

Please Log in or Create an account to join the conversation.

  • Posts: 89
  • Thank you received: 16

Replied by Adrian on topic Weather Radio - info channel

You launch the indi weatherradio service with the start command as you say.
You can also use a different syntax which gives the same result

e.g.
sudo systemctl stop indi-weatherradio.service
etc.

What you are typing is fine for controlling the service, you can use other methods but you only need one.

You need to get the output of the indiserver into a file to record what is happing in case of a crash.
To do this you need to edit the service script to redirect the output to a file.

First stop the service
Use a text editor to edit the service file /etc/systemd/system/indi-weatherradio.service

Change the exec start command from
ExecStart=/usr/bin/indiserver -v indi_weatherradio
to
ExecStart=/usr/bin/indiserver -v indi_weatherradio >> /tmp/weatherradio_output.txt

Now restart the service.
You can check if it is running with the status command (or ps aux | grep indiserver)

Now if the server crashes the log will be in /tmp/weatherradio_output.txt. You can look at that for any clues.

When you don't want the log anymore you can change the service file back to the original one.
4 months 3 weeks ago #66373

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 3
Hello
So how do I edit the file, because there's nothing I can do about it?
4 months 3 weeks ago #66440

Please Log in or Create an account to join the conversation.

  • Posts: 89
  • Thank you received: 16

Replied by Adrian on topic Weather Radio - info channel

Gain access to the box running the service, same as how you get to issue the commands to start and stop and get status for the service.

This is usually by either
- sitting at box with monitor and keyboard
- remote access over the network

At box
======
If you are using a keyboard and monitor at the computer running the service, start a terminal and edit the file with an editor, for instance
$ sudo nano /path/to/file

nano is a simple editor with prompts.

Make the changes and save the file
You can use any editor you like.

Remote access
=============
If you are remote from the computer running the service, use ssh (putty on windows) to get terminal access and proceed as before. You can also use a remote desktop instead of ssh if you have that set up.
4 months 2 weeks ago #66463

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 3
hello
then I don't have a problem to open it, but I can't modify it, because, I don't have the authorization to modify it.
4 months 2 weeks ago #66465

Please Log in or Create an account to join the conversation.

  • Posts: 89
  • Thank you received: 16

Replied by Adrian on topic Weather Radio - info channel

If you use sudo you should be able to edit it, sudo makes you the super user.

If you tried sudo and it did not work please post the command you tried and the output you got back.
4 months 2 weeks ago #66472

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 3
hello
so I managed to modify the command line, more than waiting for the next crash to see where the problem comes from.

Christophe
4 months 2 weeks ago #66479

Please Log in or Create an account to join the conversation.

  • Posts: 89
  • Thank you received: 16

Replied by Adrian on topic Weather Radio - info channel

Here are two useful commands for you to try to monitor the situation

Check that indi is working
====================
$ ps aux | grep indiserver

You should see a line saying that indiserver is working, it will include the command including indi_weatherradio

Check the output of the logfile
=======================
$ tail -f /tmp/logfilename.txt

Instead of /tmp/logfilename.txt put in the path to the log file you used in the service script

This will show the output from the indiserver being put into the log file.
-f means follow and uou need to press ^C to get your command prompt back again.

Changing verbosity of indi
====================
You can increase the amount of information that indi outputs by adding extra v to the service file.

The service file above has one v as in
indiserver -v indi_weatherradio >> /tmp/outputfile.txt

To make it more verbose use -vv or -vvv
indiserver -vv indi_weathreradio >> /tmp/outputfile.txt

Hopefully your mystery will be solved soon.
4 months 2 weeks ago #66481

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 3
hello
so here it is, it happened, my weather station crashed.
So now I'm doing how to find and read the file that will tell me what happened.
because I can't find a file

See you
Christophe
Last edit: 4 months 5 days ago by Porchet.
4 months 5 days ago #67109

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 3
hello
so I have a good look, in the "tmp" file.
there is nothing .

Why?
4 months 3 days ago #67187

Please Log in or Create an account to join the conversation.

  • Posts: 741
  • Thank you received: 203
Did your system reboot? On some systems, /tmp gets cleaned when the system is started.
TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | Moravian G2-8300 + ASI 1600mm pro | KStars/INDI on Raspberry Pi 4 with Raspbian 10
4 months 3 days ago #67189

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 3
No, I did not reboot !
4 months 3 days ago #67190

Please Log in or Create an account to join the conversation.

Time to create page: 0.712 seconds