I noticed the behavior also and IPS is initializing if you run top while everything else is still frozen. I assumed my computer was a little too slow for this cutting edge technology so didn't open a new thread[;)]
Yeah I have noticed the same thing, it usually gave me access after the last beep but now I have to wait like a minute for it to initialize. I assumed the beep was there to let you know that it is either about to shut down or about to startup and shutdown on last beep or finalize startup on last beep.
this is no bug. It depends on how much performance your system has. The beeps are a signal that the last start script of the daemons is started. But it can take some seconds until the astaro is reachable thats normal
I am sure this is not the end of this discussion. Many admins that rely on the beeps will be contacting astaro in the near future when they can't login and just give up and reboot since they can't contact their firewall after the beeps.
Astaro folks are stubborn about some really simple things. The beeps are there for a reason. They are always there for a reason on any hardware appliance. You can't just have them doing something and then say, oh yeah they just indicate all the daemons have initialized or the last script has run or whatever. Either remove the beeps or wait till IPS initializes (since it takes longer to initialize snort in this version than previous versions due to different detection method), I don't even know why we are discussing this as not a bug.