Linux Mono Logs Multiple Entries

[Buford T. Justice]

I just migrated from Windows 10 to Kubuntu GNU/Linux. I installed mono-complete and got Cumulus running just fine. I decided to look at my month log and noticed entries are being repeated:

Code: Select all

11/09/21,06:00,64.8,87,60.8,1.9,4.5,163,0.00,0.00,1014.8,31.37,79.3,59,1.6,64.8,64.8,0.0,0,0.000,0.000,67.3,0,0.0,155,0.00,0.00,66.4,22.7
11/09/21,06:05,64.9,87,61.0,1.3,2.9,154,0.00,0.00,1014.6,31.37,79.5,58,0.2,64.9,64.9,0.0,0,0.000,0.000,67.9,0,0.0,137,0.00,0.00,66.9,22.9
11/09/21,06:05,64.9,87,61.0,1.2,2.9,154,0.00,0.00,1014.6,31.37,79.5,58,0.0,64.9,64.9,0.0,0,0.000,0.000,67.9,0,0.0,0,0.00,0.00,66.9,22.9
11/09/21,06:05,64.9,87,61.0,1.2,2.9,154,0.00,0.00,1014.6,31.37,79.5,58,0.0,64.9,64.9,0.0,0,0.000,0.000,67.9,0,0.0,0,0.00,0.00,67.0,22.9
11/09/21,06:10,64.8,87,60.8,0.8,2.9,127,0.00,0.00,1014.9,31.37,79.7,58,0.4,64.8,64.8,0.0,0,0.000,0.000,67.9,0,0.0,123,0.00,0.00,66.9,22.7
11/09/21,06:15,64.8,87,60.8,0.5,1.8,122,0.00,0.00,1015.0,31.37,80.1,58,0.7,64.8,64.8,0.0,0,0.000,0.000,68.1,0,0.0,121,0.00,0.00,67.0,22.7
11/09/21,06:15,64.8,87,60.8,0.5,1.8,122,0.00,0.00,1015.0,31.37,80.1,58,0.7,64.8,64.8,0.0,0,0.000,0.000,68.1,0,0.0,121,0.00,0.00,67.0,22.7
11/09/21,06:15,64.8,87,60.8,0.5,1.8,122,0.00,0.00,1015.0,31.37,80.1,58,0.7,64.8,64.8,0.0,0,0.000,0.000,68.0,0,0.0,121,0.00,0.00,67.0,22.7
11/09/21,06:25,64.4,88,60.8,0.9,3.4,128,0.00,0.00,1014.8,31.37,79.3,59,0.2,64.4,64.4,0.0,0,0.000,0.000,67.5,0,0.0,129,0.00,0.00,66.4,22.5
11/09/21,06:25,64.2,88,60.6,0.9,3.4,128,0.00,0.00,1014.8,31.37,79.3,59,0.2,64.2,64.2,0.0,0,0.000,0.000,67.2,0,0.0,129,0.00,0.00,66.2,22.3
11/09/21,06:35,64.0,88,60.4,0.3,1.1,129,0.00,0.00,1015.0,31.37,79.7,59,1.1,64.0,64.0,0.0,0,0.000,0.000,67.3,0,0.0,129,0.00,0.00,66.1,22.2
11/09/21,06:35,64.0,88,60.4,0.4,1.1,129,0.00,0.00,1015.0,31.37,79.7,59,1.1,64.0,64.0,0.0,0,0.000,0.000,67.3,0,0.0,129,0.00,0.00,66.1,22.2

What might be causing this?

[mcrossley]

My only thought is that there are multiple copies of MX running in the background. The mxdiags file shows each log entry being written, so take a look at that.

Use the top or htop commands to show all the running processes.

[Buford T. Justice]

Htop showed a couple of Cumulus processes. After killing them, I restarted Cumulus. It appears to be working fine now. I am not sure why those other process didn't close. I thought I had hit CTRL + C when I closed earlier sessions. Actually come eto think of it, I may have closed a terminal window while Cumulus was running when I upgraded to the latest version of CumulusMX. If I did, oops. I did notice the version on the localhost webpage had not updated to the latest version so I may have had an old man moment.

[mcrossley]

Easily done, if you enable the "Stop second instance" under Program Settings, it will not let you start a second instance.

That option always used to default to off, I changed it to default to on for new users.

[Buford T. Justice]

Now I am not sure what is going on...

Code: Select all

mono CumulusMX.exe
Cumulus MX v.3.13.1 build 3146
Working Dir: /home/owner/CumulusMX/
System.IO.IOException: Directory not empty
  at System.IO.FileSystem.RemoveDirectoryInternal (System.IO.DirectoryInfo directory, System.Boolean recursive, System.Boolean throwOnTopLevelDirectoryNotFound) [0x00158] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 
  at System.IO.FileSystem.RemoveDirectory (System.String fullPath, System.Boolean recursive) [0x00024] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 
  at System.IO.Directory.Delete (System.String path, System.Boolean recursive) [0x00007] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 
  at CumulusMX.Cumulus.BackupData (System.Boolean daily, System.DateTime timestamp) [0x00081] in <5814b8d7c63844dc84841f2752608265>:0 
  at CumulusMX.Cumulus..ctor (System.Int32 HTTPport, System.Boolean DebugEnabled, System.String startParms) [0x01fc2] in <5814b8d7c63844dc84841f2752608265>:0 
  at CumulusMX.Program.RunAsAConsole (System.Int32 port, System.Boolean debug) [0x00048] in <5814b8d7c63844dc84841f2752608265>:0 
  at CumulusMX.Program.Main (System.String[] args) [0x00529] in <5814b8d7c63844dc84841f2752608265>:0 
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
Press Enter to terminate

[Buford T. Justice]

sudo mono Cumulus.exe works.

[freddie]

Looks like a permissions issue. Tried to do something in a directory but wasn't permitted to read the contents of it.

[Buford T. Justice]

Yup. While running CumulusMX as sudo, it made files in the backup folder. I had to open the backup folder in Terminal and:

Code: Select all

sudo rm -fr [FILENAME].txt
sudo rm -fr [FOLDER]

Replacing [FILENAME] or [FOLDER] with each file/folder sudo created that I couldn't delete normally in the Dolphin file explorer.

It is running fine now with mono CumulusMX.exe