Assertion if no Network available

Raziel · Post by **Raziel** » Thu Apr 19, 2012 12:27 pm

assertion "RequesterBase != NULL" failed: file "autoinit_requester_base.c", line 34

I get this everytime on startup if my router has no internet connection (and *ONLY* then).

I assume it's one of the programs that need internet access or check for it on startup.
Sadly i don't know which and even more sadly this assertion will stop the boot process with no cure other than to reboot (although it *very seldomly* boots through to Workbench leaving me with no internet access).

I found the "RequesterBase != NULL" part in Prefs/WBStartup, Prefs/Notifications, System/RinghioServer, Utilities/Installation Utility, Utilities/InstallExtras/Extras Installer and Utilities/LogViewer (at least that is what "Find" gave me)

If it is one of them that is asserting(?) than either WBStartup (started first) or RinghioServer (first program in WBStartup) or Notifications (started by RinghioServer i think)

On the other hand it could also be the network stack, but i don't know nothing about the internals of OS4.

Can i do something about it to corner this or is it already in the bugtracker or should i go away?

Post by **tonyw** » Fri Apr 20, 2012 5:58 am

It can't be caused by any of the Prefs/ editors, since they aren't called at boot time. Likewise the Utilities components you mentioned.

That leaves only the Ringhio server, and I can't think of any reason why that should want or need a network. Perhaps "RequesterBase" is not an accurate description?

I haven't heard of this before, so maybe it is something peculiar to your system. What are you running? Do you have the "Run >NIL:" prefix to the AddNetInterface call? If so, what happens if you force it to complete before S-S continues?

Raziel · Post by **Raziel** » Fri Apr 20, 2012 8:39 pm

tonyw wrote:It can't be caused by any of the Prefs/ editors, since they aren't called at boot time. Likewise the Utilities components you mentioned.

That leaves only the Ringhio server, and I can't think of any reason why that should want or need a network. Perhaps "RequesterBase" is not an accurate description?

I haven't heard of this before, so maybe it is something peculiar to your system. What are you running? Do you have the "Run >NIL:" prefix to the AddNetInterface call? If so, what happens if you force it to complete before S-S continues?

I have a "fixed" XE, maybe thats the problem

I am not on my miggy so i cant tell you what is loaded on boot time (WBStartup hs not been reached yet) but maybe it helps if i tell you that i had it the first time with update 2.

I have the run >NIL: before that line and if i leave it to finish before S-S continues it will simply sit there waiting for a network...forever...and will kick in as soon as one has been found...if ever.

Raziel · Post by **Raziel** » Sat Apr 21, 2012 2:08 pm

Raziel wrote:...(WBStartup hs not been reached yet) but maybe it helps if i tell you that i had it the first time with update 2.

I should stop posting after a long day in work :-/

of course it reaches WBStartup, scrap that

What i meant to say was that i get this error message solely printed on the initial shell window (which sotherwise is never displayed before WB comes up - apart from if somehing went wrong in the boot process). That makes me wonder if the error is caused by some program from startup-sequence or user-startup (that is actually addressing a website) and that brings me to the only program i have that does this

I have this line as last command in user-startup

c:date server de.pool.ntp.org save (dont quote me on the server address, im doing this from memory

)

which tries to grab the time from the given time server and save it to the battery.

Could this be causing it?
I also remember that i started using this line with update 2
(which covers my comment in the last post about the first time it happened)

Could it, if it is the bad guy, be "fixed" in a way that it wont throw an assertion but rather print an error message about the network not found?

Thank you very much for your time

Post by **nbache** » Sun Apr 22, 2012 12:15 am

Raziel wrote:
Raziel wrote:I have this line as last command in user-startup

c:date server de.pool.ntp.org save (dont quote me on the server address, im doing this from memory )

which tries to grab the time from the given time server and save it to the battery.

Could this be causing it?

Definitely a possibility, although I've never seen it happen myself.

But you could easily test the theory by commenting out that line in your user-startup (why user-startup, BTW, why not network-startup?).

BTW, you don't have to have the server name explicitly in the command; if you have set up your Time prefs with the server details on the remote tab page and saved them, you can just use "C:Date server prefs". Also, there is no such thing as a "save" switch on date (only on SetClock), but hopefully that's just your memory failling you at the time of posting.

Best regards,

Niels

Raziel · Post by **Raziel** » Sun Apr 22, 2012 3:24 pm

nbache wrote:
Raziel wrote:
Raziel wrote:I have this line as last command in user-startup

c:date server de.pool.ntp.org save (dont quote me on the server address, im doing this from memory )

which tries to grab the time from the given time server and save it to the battery.

Could this be causing it?
Definitely a possibility, although I've never seen it happen myself.

But you could easily test the theory by commenting out that line in your user-startup (why user-startup, BTW, why not network-startup?).

Hmm...network-startup?
I remember reading about such a startup file, but i thought it was a third party achievement (that would explain why i lost it with the last update)???

BTW, you don't have to have the server name explicitly in the command; if you have set up your Time prefs with the server details on the remote tab page and saved them, you can just use "C:Date server prefs". Also, there is no such thing as a "save" switch on date (only on SetClock), but hopefully that's just your memory failling you at the time of posting.

Best regards,

Niels

Yes, thats one of my memory fails, it is of cource c:date server PREFS (i will get rid of the server line of course)
and comment it out to see if it is the bad guy (when i get back to my miggy)

Thanks for the hints guys

Post by **nbache** » Sun Apr 22, 2012 11:30 pm

Raziel wrote:Hmm...network-startup?
I remember reading about such a startup file, but i thought it was a third party achievement (that would explain why i lost it with the last update)???

My fault, sorry.

Network-Startup is an Update 5 thing, so unless you have an X1000, you won't have seen it yet (at least not as an "official" component). But it is the same in principle as the ones we have been discussing on the web fora a couple of times: Run Execute S:Network-Startup (with the usual NIL: redirections) instead of AddNetInterface in Startup-Sequence, and then in Network-Startup start by doing AddNetInterface (without Run) and continue with other network-related stuff - like for example that Date SERVER PREFS command.

But if you have your Date command in User-Startup, I hope you didn't put Run in front of your AddNetInterface command in Startup-Sequence? Because then your network will be starting in parallel with the rest of your Startup-Sequence and User-Startup, and you will have no way of ensuring the network is actually up when User-Startup gets to the Date command - which might possibly be the situation you see.

Best regards,

Niels (who is glad Update 5 is public knowledge at least with First Contact buyers, otherwise I'd have accidentally broken my NDA

).

Raziel · Post by **Raziel** » Tue Apr 24, 2012 2:10 am

nbache wrote:
Raziel wrote:Hmm...network-startup?
I remember reading about such a startup file, but i thought it was a third party achievement (that would explain why i lost it with the last update)???
My fault, sorry.

Network-Startup is an Update 5 thing, so unless you have an X1000, you won't have seen it yet (at least not as an "official" component). But it is the same in principle as the ones we have been discussing on the web fora a couple of times: Run Execute S:Network-Startup (with the usual NIL: redirections) instead of AddNetInterface in Startup-Sequence, and then in Network-Startup start by doing AddNetInterface (without Run) and continue with other network-related stuff - like for example that Date SERVER PREFS command.

But if you have your Date command in User-Startup, I hope you didn't put Run in front of your AddNetInterface command in Startup-Sequence? Because then your network will be starting in parallel with the rest of your Startup-Sequence and User-Startup, and you will have no way of ensuring the network is actually up when User-Startup gets to the Date command - which might possibly be the situation you see.

Best regards,

Niels (who is glad Update 5 is public knowledge at least with First Contact buyers, otherwise I'd have accidentally broken my NDA ).

Ahh, ok

I still have the run in front of AddNetInterface and yes, it only happens when there is no network available...
That might be it then.

Can anyone check if "date" has a fallback if no network access is possible, please? (apart from the assertion?)
And probably file a bug item for me to add such a (non-blocking) fallback?
An error requester might be nice?

Thanks Niels for the help

xenic · Post by **xenic** » Tue Apr 24, 2012 5:49 am

Raziel wrote: Can anyone check if "date" has a fallback if no network access is possible, please? (apart from the assertion?)
And probably file a bug item for me to add such a (non-blocking) fallback?
An error requester might be nice?

When I run the "date SERVER..." command without the network running I get this message:
DATE: Couldn't get remote time: Host name lookup failure

However, I noticed another problem. Netshutdown doesn't work after I have run "date SERVER... " and it just times out. After the timeout I get a Grim Reaper if a program tries to access the network. I don't use the date command to set my system time in my startup-sequence and it looks like I won't in the future based on how it affects my system.

With reference your other topic about not being able to restart your network after using NetShutdown; maybe you should try removing (commenting out) the date command in your startup and see if that affects your ability to shut down and restart your network.

Raziel · Post by **Raziel** » Wed Apr 25, 2012 12:56 pm

xenic wrote:
Raziel wrote: Can anyone check if "date" has a fallback if no network access is possible, please? (apart from the assertion?)
And probably file a bug item for me to add such a (non-blocking) fallback?
An error requester might be nice?
When I run the "date SERVER..." command without the network running I get this message:
DATE: Couldn't get remote time: Host name lookup failure

However, I noticed another problem. Netshutdown doesn't work after I have run "date SERVER... " and it just times out. After the timeout I get a Grim Reaper if a program tries to access the network. I don't use the date command to set my system time in my startup-sequence and it looks like I won't in the future based on how it affects my system.

With reference your other topic about not being able to restart your network after using NetShutdown; maybe you should try removing (commenting out) the date command in your startup and see if that affects your ability to shut down and restart your network.

It's not the date command, but i can confirm the ISI crash of c:date if bsdsocket.library is not available

Hidden Text - Click to Show :

I'll keep on searching, right now it's a little hit and miss but i got a few more candidates that might be it

Thanks guys

Hyperion Entertainment Message Boards

Assertion if no Network available

Assertion if no Network available

Re: Assertion if no Network available

Re: Assertion if no Network available

Re: Assertion if no Network available

Re: Assertion if no Network available

Re: Assertion if no Network available

Re: Assertion if no Network available

Re: Assertion if no Network available

Re: Assertion if no Network available

Re: Assertion if no Network available