Hi!

The scenario:

Neorouter is installed in an ubuntu-image.
The technician installs a box with the image at a customer location.
Then logs in to neorouter, a professional edition (latest).
He then logs in just fine.

I then log in remotely, to finish up the configurations, to set site spesific configs, including hostname. After a reboot, the neorouter client won't connect. When I try to rerun the cmd tool and puts in the correct domain, user, and password, it just hangs at "Connecting to neorouter client service"
When i reinstall the neorouter client, it works fine again.

Is there a way around this behaviour?

The reason I need this to work, is to make the customers able to install the boxes themselves, and not having to configure the site spesific settings until the box is in place.

Hi kaa4re,

Changing hostname does not affect NR client. There would be something else having problem. We cannot reproduce it in our lab.

Can you reproduce it? If you can collect the log file when it cannot connect, it may help us to investigate it.

Btw, please check
1. If the physical network up at the moment?
2. If the nrservice process is running.

Let us know if you have any clue, such as changing MAC address or so.

Thanks,
KevinZ - NeoRouter team

Thanks!

I've checked a bit, and found that the ubuntu box uses quite some time to get online. These ar machines for remote locations with 3G/GPRS cards in them, and it seems the nrservice fails to start when it's not connected to the internet.

What I need is for nrservice to keep trying to connect.

Is there any config options I've overlooked?

Okay, got an update.
I've tried different approaches, what i see now, is that the service simply fails to start during boot.

I suspected internet-connectivity at first, since it takes a bit of time to get online with the 2G/3G modem, but when i tried a couple of combinations it didn't seem to matter. If i start the service via the init-script after boot, it works just fine, even if the modem is unplugged, it starts up, and goes online as soon as it's reconnected.
Also if i remove the modem with the service running, it's reconnecting as expected. In other words it's just the startup issue left.

It seems that the startup job get initialized, but something is preventing a succesfol start.
I find this in my dmesg:
[ 5.519887] init: nrservice main process (1044) terminated with status 1
[ 5.519970] init: nrservice main process ended, respawning
[ 5.536667] init: nrservice main process (1046) terminated with status 1
[ 5.536740] init: nrservice main process ended, respawning
[ 5.555083] init: nrservice main process (1048) terminated with status 1
[ 5.555149] init: nrservice main process ended, respawning
[ 5.570312] init: nrservice main process (1050) terminated with status 1
[ 5.570410] init: nrservice respawning too fast, stopped
This is the only trace I can find of the nrserver during startup.