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

Trouble taking a backup

#1
Hi,
I wanted to give the Backup procedure a try, but nothing happens...

When I first chose 'Backup', I was asked a username and password which I entered. After that I could see the URL in the browser location bar: http://192.168.0.28/backup/backup.nems.
So I assumed that the backup would be in /var/www/html/backup. However the only file in there is index.php.

When I tried this for the second time, no username and password was requested and nothing happened.
I had a look at several logfiles:
migrator-backup-runtime.log has number 7 in it.
messages: showed nothing related
When I look at the backup.sh script, it requires to be run by root...
Is there some setting I overlooked?
 Reply
#2
There's nothing you need to look at there, but your migrator is for some reason missing a setting (as can be told by the statement that there is only an index.php).

What version of NEMS are you running? Type nems-info nemsver
Robbie Ferguson, Host
Category5 Technology TV
www.Category5.TV
254-5-CAT5TV
 Reply
#3
As a side note - mind posting the output of this command?  sudo nems-update

The problem you're experiencing was patched a while ago, so I just want to make sure your nems-scripts are updating correctly (they might fail if you edited any of the files in that folder).
Robbie Ferguson, Host
Category5 Technology TV
www.Category5.TV
254-5-CAT5TV
 Reply
#4
I'm running nems 1.2.3.

However there is no nems-info command...

Here is the output of sudo nems-update:


Code:
[email protected]:~ $ sudo nems-update
PING google.com(ams15s29-in-x0e.1e100.net (2a00:1450:400e:806::200e)) 56 data bytes
64 bytes from ams15s29-in-x0e.1e100.net (2a00:1450:400e:806::200e): icmp_seq=1 ttl=53 time=44.4 ms

--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 44.416/44.416/44.416/0.000 ms
Updating nems-migrator... fatal: unable to access 'https://github.com/Cat5TV/nems-migrator/': Couldn't connect to server
Done.
Updating nems-www... fatal: unable to access 'https://github.com/Cat5TV/nems-www/': Couldn't connect to server
Done.
Updating nems-scripts... fatal: unable to access 'https://github.com/Cat5TV/nems-scripts/': Couldn't connect to server
Done.
Running updates and fixes... Done.


Looks like something is wrong here...
 Reply
#5
Yes, that confirms why you're having trouble. NEMS has to be able to use git to update itself (and part of that is setting up your NEMS-Migrator backup set).

Are you blocking git, github.com, or any other reason we'd be seeing this?
Robbie Ferguson, Host
Category5 Technology TV
www.Category5.TV
254-5-CAT5TV
 Reply
#6
By the way, since nems-upgrade also uses git, if this problem existed during a nems-upgrade, it may say you are running NEMS 1.2.3 but in actuality you are running NEMS 1.2.1. This could cause all kinds of issues, so I'm interested to know why git is failing on your network.

I've noted to add some error handling in case of this, but very curious as to the "why".
Robbie Ferguson, Host
Category5 Technology TV
www.Category5.TV
254-5-CAT5TV
 Reply
#7
Not that I am aware of, but I cannot ping github.com.

For the installation of nems, I used the image on your site and then did a nems-update. Did not touch anything else...



Code:
[email protected]:~ $ ping github.com
connect: Netwerk is onbereikbaar

Which means 'Network unreachable'...

I can ping other sites without a problem.
Code:
[email protected]:~ $ ping forum.category5.tv
PING forum.category5.tv(2400:cb00:2048:1::681c:166d (2400:cb00:2048:1::681c:166d)) 56 data bytes
64 bytes from 2400:cb00:2048:1::681c:166d (2400:cb00:2048:1::681c:166d): icmp_seq=1 ttl=57 time=22.1 ms
64 bytes from 2400:cb00:2048:1::681c:166d (2400:cb00:2048:1::681c:166d): icmp_seq=2 ttl=57 time=20.7 ms
64 bytes from 2400:cb00:2048:1::681c:166d (2400:cb00:2048:1::681c:166d): icmp_seq=3 ttl=57 time=23.7 ms
64 bytes from 2400:cb00:2048:1::681c:166d (2400:cb00:2048:1::681c:166d): icmp_seq=4 ttl=57 time=21.8 ms


From another machine that I use I can ping github.com without a problem, so no blocking at router level or something.


Code:
[[email protected] ~]$ ping github.com
PING github.com (192.30.253.113) 56(84) bytes of data.
64 bytes from lb-192-30-253-113-iad.github.com (192.30.253.113): icmp_seq=1 ttl=53 time=104 ms
64 bytes from lb-192-30-253-113-iad.github.com (192.30.253.113): icmp_seq=2 ttl=53 time=105 ms
64 bytes from lb-192-30-253-113-iad.github.com (192.30.253.113): icmp_seq=3 ttl=53 time=106 ms

Interesting, I cannot traceroute the host I can ping...

Code:
[email protected]:~ $ traceroute forum.category5.tv
traceroute to forum.category5.tv (104.28.22.109), 30 hops max, 60 byte packets
connect: Netwerk is onbereikbaar

 Reply
#8
Yeah, the image is not the problem. For some reason your NEMS server can't communicate with github, and I did not account for that with nems-upgrade - so that means while your NEMS server says it is NEMS 1.2.3 it is not. The update would have failed and since I never accounted for that, it would have still rolled up the version number.

It's easy to fix - but we need to figure out why you can't see github.com. I am thinking it might be a DNS issue - perhaps a setting on NEMS is specific to my region on the American continent, so causing an issue where you are.

Is there any possibility of me gaining SSH access to your NEMS server? I'd gladly take a look at this for you tomorrow, and will also fix the versioning for you.
Robbie Ferguson, Host
Category5 Technology TV
www.Category5.TV
254-5-CAT5TV
 Reply
#9
I found out what the reason is...

I wanted to have the NEMS server a static IP address, but as I have no control over my router as that is handled by my ISP, I cannot assign IP addresses on the router.

So I used the Webmin interface to do that and then did 

Code:
echo "denyinterfaces eth0" >> /etc/dhcpcd.conf



However the gateway address was not set...

I can add the gateway address with

Code:
sudo route add default gw 192.168.0.1 eth0


But that gets lost after a reboot...

While I was having the correct gateway, I took the opportunity to run nems-update and now it did really update!
Now I need to figure out which file to edit to set the gateway permanently...


PS: Backup works!
 Reply
#10
Fantastic, and well done!

Now, one more thing I'd like you to do... I wrote this command for you.

Code:
sudo nems-update && sudo nems-upgrade reset


That'll fix the version issue since github wasn't available, and will correct any damage that caused.

Information may be found in the NEMS Documentation.
Robbie Ferguson, Host
Category5 Technology TV
www.Category5.TV
254-5-CAT5TV
 Reply
 
 
Forum Jump:

Users browsing this thread: 1 Guest(s)