On server: -rw-r--r-- 1 ossecr ossec 70K Июн 3 05:32 merged.mg On client's OS merged.mg has full access for Administrators group, but I think it does not matter, since the ossec service started with the SYSTEM rights. As I said earlier, 95% of clients are working without problems...
вторник, 2 июня 2015 г., 17:02:28 UTC+3 пользователь dan (ddpbsd) написал: > > On Tue, Jun 2, 2015 at 5:06 AM, Maksim Mohilko <[email protected] > <javascript:>> wrote: > > Hi all! > > > > There is the following connection scheme: Client (Windows XP) - Router > > (Firewall) - Server. Port 1514 is open. OS on Client is all the same, > it is > > installed from a single image. Router configuration is also the same. > 95% of > > agents work fine, but the 5% has the following problem. When a client > > connects to the server, no configuration files are downloaded to the > folder > > SHARED, only the merged.mg file. Also merged.mg file a long time has > zero > > size. > > Write permissions to the SHARED folder are standard, with the main > > configuration file (ossec.conf) agent works fine, just can not pull an > > additional configuration files (i.e. agent.conf). Has anyone experienced > > this? Prompt, in what could be the problem? > > > > Thanks in advance! > > > > Check the permissions and ownership of the merged.mg file. > > > -- > > > > --- > > You received this message because you are subscribed to the Google > Groups > > "ossec-list" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
