Atomicorp

Hm, how do you mean?

Should I add
publicip my.correct.servername
to /etc/hosts?

Right now the server resolves my.correct.servername to 127.0.0.1

Every time i run asl -s -f I get this message. tortixd: Could not reliably determine the server's fully qualified domain name, using "my.correct.servername" for ServerName Anyone know why? It's nothing new, I have seen it for quite some time, but as everything is working, I haven't thought...

try this tip from Scott
https://atomicorp.com/forums/viewtopic. ... _fw#p40170

Yes, always install ASL by the end.

What you are describing certainly points in the direction of the name servers still pointing to the old provider. Do a check with nslookup och dig.

Thanks a lot for the explanation. The reason I though nothing was happening was that I had not seen any update for two weeks and even asked for the current status without any reply. When you get an email every hour you tend to loose patience quicker and actually thought it had been forgotten. I'm re...

Sorry, should of course included the case number, 29079

Not sure it's the same problem but I'm having a big trouble with rules sending email even if email is turned off and level lowered. In the support ticket I was told to update to ASL 4 which I have been running for two weeks now. The problem is still there and the support ticket isn't updated anymore...

I would love to have a re-direct to http://www.ie6countdown.com/educate-others.aspx

When reading the page you refer to I clearly says that you only need to be PCI compliant if you use the API. You can still use there hosted PRO solution, but not the API without PCI certification.

Nope, got it from the tortix channel.

No chance Lance

I was in the stable channel. I installed it and then it broke. I downgraded and everything worked. Then I run yum update again and the upgrade was offered again. The day after the upgrade was gone. True story...

Strange. I have not enabled the testing channel and still got the update.

edit: checked again. Now it has been removed. I guess someone read my post...

Ok, thanks. Maybe ossec-hids 2.7 only should be published in testing channel as well?

I just updated to ossec-hids-2.7-32.el6.art.x86_64 and then ossec refused to start. No errors in the log file, just these lines being repeated with each restart: tail -n 7 /var/ossec/logs/ossec.log 2013/10/16 09:27:31 ossec-testrule: INFO: Reading decoder file etc/decoder.xml. 2013/10/16 09:27:31 os...