Linux Mint 20.2, FT-818, Digirig sound+CAT, WSJT-X 2.5.1
Initial install worked for a while....transmitter locked on......couldn't terminate WSJT-X.....forced reboot.

I uninstalled WSJT-X, reinstalled it. Can't start WSJT-X because I get the message that another instance is running. Options in messaage don't work.

Help, Help....I'm dead in the water here.

Ken, KB4XT

Linux Mint 20.2, FT-818, Digirig sound+CAT, WSJT-X 2.5.1
Initial install worked for a while....transmitter locked on......couldn't terminate WSJT-X.....forced reboot.

I uninstalled WSJT-X, reinstalled it. Can't start WSJT-X because I get the message that another instance is running. Options in messaage don't work.

Help, Help....I'm dead in the water here.

Ken, KB4XT

Hi Ken,

are you certain there is not anther instance of WSJT-X running? The "Yes" option in that message box should be able to remove the lock if there is no other instance running.

The lock is a file with this path:

/tmp/WSJT-X.lock

What are the ownership and permissions on that file?

ls -l /tmp/WSJT-X.lock

If all seems normal then use the `lsof` utility to find out which process has the lock file open:

lsof /tmp/WSJT-X.lock

If your system doesn't have `lsof` installed you can get it by installing the `lsof` package:

sudo apt install lsof

73
Bill
G4WJS.

Bill,
. 
Thanks a bunch.

It was locked up and pressing Yes would not remove the other copy. After a while including uninstall, reinstall, I gave up and wrote the note above. Then I powered-down and left it. This morning when I turned the ASUS laptop back on. All was fine. WSJT-X opened without the "Another Instance" message. When I connected it to the FT-818 and digirig....I found that the setup was still there, even after reinstalling. I made a successful contact...so all is well NOW.

At any rate, I appreciate the response. I will keep the info handy for the case that the problem returns.

Thank You, Thank You....!!!!!!

Ken, KB4XT

FWIW ... I always restart the computer when I see an error like that.  Restarting (no matter what OS) will normally clear the environment, and release any files that are locked.

Your shutdown in Linux did the same, although when using Windows its best to do a restart as it acts somewhat differently when you shutdown.

Neil, KN3ILZ

Bill,

The problem came back. I executed the two items that you told me to check. Results below.

Bill,

The problem came back. I executed the two items that you told me to check. Results below.

ken@ken-X510UNR:~$ ls -l /tmp/WSJT-X.lock

-rw-rw-r-- 1 ken ken 93 Oct 28 14:38 /tmp/WSJT-X.lock

ken@ken-X510UNR:~$ 

 

 

COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF    NODE NAME

wsjtx   1944  ken   11uW  REG   8,18       93 4849681 /tmp/WSJT-X.lock

ken@ken-X510UNR:~$ 

I started off on 40m  and made a contact. Then, moved to 20m. TX locked to on after responding to cq. Turned pwr off radio. closed wsjt-x but wouldn't restart, same Another Instance message. The YES nor any of the other options worked. Exited Mine Forced closure wsjtx. Back to cold restart of computer....wsjtx came up. Now won't TX, in response to cq or Tune.

Thanks,

Ken KB4XT

Hi Ken,

the second result is showing that a process running wsjtx with PID 1944 is holding the lock. That means the previous run of WSJT-X is not closing down promptly, that can happen if CAT connections have been lost, e.g. turning the rig off before closing WSJT-X.

73
Bill
G4WJS.

Bill,

You are so correct as usual. I found that the cables supplied by Digirig were faulty. I changed to a combination of Signalink and a CAT cable...forgot name. So far things seem to be working just fine.

I do appreciate your help.

Ken, KB4XT