Hello There, Guest!  
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Fixed - Issues with NEMS update causing stats not to work.

#1
GOOD MORNING Robbie,

Here's the thread I said I'd get opened up as we discussed via Twitter DM. These were the results of the commands you asked me to run on my NEMS device on my home network:

[email protected]:~ $ sudo nems-update
PING google.com (216.58.217.206) 56(84) bytes of data.
64 bytes from lax17s05-in-f14.1e100.net (216.58.217.206): icmp_seq=1 ttl=54 time=13.1 ms

--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 13.153/13.153/13.153/0.000 ms
Updating nems-migrator... Already up-to-date.
Done.
Updating nems-www... Already up-to-date.
Done.
Updating nems-scripts... /usr/local/bin/nems-update: line 34: cd: /usr/local/share/nems/nems-scripts: No such file or directory
Already up-to-date.
Done.
Running updates and fixes... /usr/local/bin/nems-update: line 43: /usr/local/share/nems/nems-scripts/fixes.sh: No such file or directory
Done.

[email protected]:~ $ sudo /home/pi/nems-scripts/stats.sh
/usr/local/bin/nems-info: line 57: /usr/local/share/nems/nems-scripts/info2.sh: No such file or directory
/usr/local/bin/nems-info: line 83: /usr/local/share/nems/nems-scripts/info2.sh: No such file or directory
[email protected]:~ $


And before you ask... no... I didn't do any tinkering with any of the scripts since the last time. Not at all.   LOL   Big Grin
"You can watch things happen, you can make things happen or you can wonder what the hell just happened." - Captain Phil Harris - Deadliest Catch
 Reply
#2
Thanks for the report.

First of all, your subject says this is part of the upgrade to NEMS 1.3, but it looks like NEMS 1.2 to me. Can you please confirm your version?

It looks to me as though a previous patch failed leaving you in an inconsistent state.

Can you please run this commands and post the output?

Code:
sudo ls -lah /usr/local/bin/nems-update && sudo ls -lah /home/pi/ & sudo ls -lah /usr/local/share/ && sudo ls -lah /usr/local/share/nems/


Thanks!
Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:
 Reply
#3
Yeah... I'm currently on the last update we did some time ago which would put me at the 1.2 version right now. Here is the output:

[email protected]:~ $ sudo ls -lah /usr/local/bin/nems-update && sudo ls -lah /home/pi/ & sudo ls -lah /usr/local/share/ && sudo ls -lah /usr/local/share/nems/
[1] 24929
total 36K
drwxrwsr-x  9 root staff 4.0K Nov  4 00:00 .
drwxrwsr-x 10 root staff 4.0K Mar 18  2016 ..
drwxrwsr-x  2 root staff 4.0K Mar 18  2016 ca-certificates
drwxrwsr-x  2 root staff 4.0K Apr 14  2016 fonts
drwxrwsr-x  3 root staff 4.0K May  3  2017 man
drwxr-sr-x  2 root staff 4.0K Nov  5 00:01 nems
drwxrwsr-x  3 root staff 4.0K May  3  2017 perl
drwxrwsr-x  7 root staff 4.0K Apr 29  2017 sgml
drwxrwsr-x  6 root staff 4.0K Apr 29  2017 xml
lrwxrwxrwx 1 root staff 31 Oct 25 00:00 /usr/local/bin/nems-update -> /home/pi/nems-scripts/update.sh
total 16K
drwxr-sr-x 2 root staff 4.0K Nov  5 00:01 .
drwxrwsr-x 9 root staff 4.0K Nov  4 00:00 ..
-rw-r--r-- 1 root root    58 Nov  6 00:00 nems.conf
-rw-r--r-- 1 root root    58 Nov  5 00:00 nems.conf~
[email protected]:~ $ total 44K
drwxr-xr-x 5 pi   pi   4.0K Nov  4 00:07 .
drwxr-xr-x 4 root root 4.0K Aug 18 09:12 ..
-rw------- 1 pi   pi   1.7K Nov  7 03:28 .bash_history
-rw-r--r-- 1 pi   pi    220 Mar 18  2016 .bash_logout
-rw-r--r-- 1 pi   pi   3.5K Mar 18  2016 .bashrc
-rw-r--r-- 1 root root 1.2K May 22 07:55 changelog.txt
drwxr-xr-x 2 pi   pi   4.0K Apr 29  2017 .nano
drwxr-xr-x 4 pi   pi   4.0K Nov  7 03:23 nems-scripts
-rw-r--r-- 1 pi   pi    675 Mar 18  2016 .profile
-rw-r--r-- 1 pi   pi     66 Apr 24  2017 .selected_editor
drwx------ 2 pi   pi   4.0K May  5  2017 .w3m
"You can watch things happen, you can make things happen or you can wonder what the hell just happened." - Captain Phil Harris - Deadliest Catch
 Reply
#4
So it looks like the patch I pushed out to NEMS 1.2.x last night already took effect on your system.

Can you run this command again?
Code:
sudo nems-update


If I'm not mistaken, the patch from last night should have already resolved your issue.
Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:
 Reply
#5
Type this please:
Code:
sudo ls -lah /usr/local/share/nems/nems-scripts

Note: 4.0K Nov  7 03:23 nems-scripts - at 3:23am my patch took effect.
Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:
 Reply
#6
OK, here's what I got this time:

[email protected]:~ $ sudo nems-update
PING google.com (172.217.11.174) 56(84) bytes of data.
64 bytes from lax28s15-in-f14.1e100.net (172.217.11.174): icmp_seq=1 ttl=54 time=13.9 ms

--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 13.996/13.996/13.996/0.000 ms
Updating nems-migrator... Already up-to-date.
Done.
Updating nems-www... Already up-to-date.
Done.
Updating nems-scripts... /usr/local/bin/nems-update: line 34: cd: /usr/local/share/nems/nems-scripts: No such file or directory
Already up-to-date.
Done.
Running updates and fixes... /usr/local/bin/nems-update: line 43: /usr/local/share/nems/nems-scripts/fixes.sh: No such file or directory
Done.

[email protected]:~ $ sudo ls -lah /usr/local/share/nems/nems-scripts
ls: cannot access '/usr/local/share/nems/nems-scripts': No such file or directory
[email protected]:~ $
"You can watch things happen, you can make things happen or you can wonder what the hell just happened." - Captain Phil Harris - Deadliest Catch
 Reply
#7
Thanks.
Now, do this:
Code:
sudo ls -lah /usr/local/share/nems

Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:
 Reply
#8
Got this:

[email protected]:~ $ sudo ls -lah /usr/local/share/nems
total 16K
drwxr-sr-x 2 root staff 4.0K Nov  5 00:01 .
drwxrwsr-x 9 root staff 4.0K Nov  4 00:00 ..
-rw-r--r-- 1 root root    58 Nov  6 00:00 nems.conf
-rw-r--r-- 1 root root    58 Nov  5 00:00 nems.conf~
[email protected]:~ $
"You can watch things happen, you can make things happen or you can wonder what the hell just happened." - Captain Phil Harris - Deadliest Catch
 Reply
#9
Alright - great thank you. I see the problem now.

Is there any chance I could SSH in and write an appropriate patch (save the back and forth commands)?
Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:
 Reply
#10
Absolutely (as we discussed on the IRC channel). I've get everything setup now to allow you to do that. Let me know as soon as you're ready and I can either DCC Message you directly on the IRC channel, DM you on Twitter or what ever other method you'd like.
"You can watch things happen, you can make things happen or you can wonder what the hell just happened." - Captain Phil Harris - Deadliest Catch
 Reply
 
 
Forum Jump:

Users browsing this thread: 1 Guest(s)