Yes - you turn on the Viruschecker service first by running that command. I mentioned to check the viruschecker status (server_viruschk) after you start the service - to ensure that the AV servers are ONLINE and CAVA working fine.
That's a correct command to start the Viruschecker (CAVA) service on the data mover. Not sure what changes were made during the migration - but if you only stopped the viruschecker on the data mover, you can start the service and everything should work.
However, please ensure the CAVA server(s) is (are) working properly along with the AV server. On the nas side - you may run server_viruschk server_2 command to find out that AV servers are ONLINE.
We have mentioned this few times earlier - you are carrying an EMC tag - i.e you are having EMC internal access - so, please use the internal Celerra forum for all your questions or queries. If you need any assistance, please contact me or others in person.
It seems, your error is having some syntax error in the viruschecker.conf file not in the command.
To echo Sandip - be sure to check the viruschecker.conf file for correctness - and blank spaces! I had a .conf file with a carriage return at the end; this file had no troubles on my NS80 but my NS20 refused to start with it. I removed the space on the NS20 and had no issues - my case may be a one-off, but it might not hurt to check.
When files are waiting to be scanned by the CAVA servers, they go into a queue. When there are sufficient CAVA servers, and the servers are lightly loaded, the queue stays (relatively) small. If the number of scanning requests increase or the time to scan each file increases, the queue can get quite large. By default, CAVA will post a LOW watermark message when the number of files waiting to be scanned exceeds 50, and will post a HIGH watermark message when the number of files waiting to be scanned exceeds 200.
Assuming there are no major issues with the Celerra, the simplest solution is to add more CAVA servers to the pool (it's pretty easy to do, and can be done "live", without stopping/restarting CAVA). Or, you can exclude more filetypes, reducing the scan load.
If you often see HIGH watermark messages, it's usually sign that there are not enough CAVA servers, or something is preventing the CAVA servers from doing real work (maybe virus DAT updates are happening too frequently, or are happening on all the CAVA servers at the same time?)
nandas
4 Operator
•
1.5K Posts
0
January 19th, 2010 11:00
Yes - you turn on the Viruschecker service first by running that command. I mentioned to check the viruschecker status (server_viruschk) after you start the service - to ensure that the AV servers are ONLINE and CAVA working fine.
Thanks,
Sandip
nandas
4 Operator
•
1.5K Posts
1
January 19th, 2010 08:00
That's a correct command to start the Viruschecker (CAVA) service on the data mover. Not sure what changes were made during the migration - but if you only stopped the viruschecker on the data mover, you can start the service and everything should work.
However, please ensure the CAVA server(s) is (are) working properly along with the AV server. On the nas side - you may run server_viruschk server_2 command to find out that AV servers are ONLINE.
Thanks,
Sandip
DHoffman2
2 Intern
•
306 Posts
0
January 19th, 2010 10:00
So, this is what I get when I run the following.
[nasadmin@CELXYZ ~]$ server_viruschk server_2
server_2 :
ERROR: Virus checker NOT started.
Error 13158645764: server_2 : ERROR: Virus checker NOT started.
So, in order to START the viruschecker, run the command I opened the question with, correct?
demenas1
2 Posts
0
January 19th, 2010 14:00
server_setup server_2 -Protocol viruschk -option start is correct
Then server_viruschk to validate
Steve
shiela_rb
14 Posts
0
March 29th, 2010 00:00
Hi All,
I also encountered the same problem eventhough the syntaz was correct..
I cannot start the vc clien. Please see below error.
[nasadmin@Celerra01 ~]$ server_setup server_2 -Protocol viruschk -option start
server_2 :
ERROR: Invalid syntax.
Error 13158645770: server_2 : ERROR: Invalid syntax.
Thanks!
Regards,
shiela
nandas
4 Operator
•
1.5K Posts
0
March 29th, 2010 11:00
Shiela,
We have mentioned this few times earlier - you are carrying an EMC tag - i.e you are having EMC internal access - so, please use the internal Celerra forum for all your questions or queries. If you need any assistance, please contact me or others in person.
It seems, your error is having some syntax error in the viruschecker.conf file not in the command.
Thanks,
Sandip
umichklewis_ac7b91
300 Posts
0
March 30th, 2010 14:00
To echo Sandip - be sure to check the viruschecker.conf file for correctness - and blank spaces! I had a .conf file with a carriage return at the end; this file had no troubles on my NS80 but my NS20 refused to start with it. I removed the space on the NS20 and had no issues - my case may be a one-off, but it might not hurt to check.
Karl
DHoffman2
2 Intern
•
306 Posts
0
April 1st, 2010 05:00
Since this topic has had recent activity, maybe I'll add to this. First, the information here was correct and I just marked the question as answered.
Second. Just recently, I have been getting LOW and HIGH watermark messages in the GUI. Typically, what causes this?
umichklewis_ac7b91
300 Posts
0
April 1st, 2010 05:00
When files are waiting to be scanned by the CAVA servers, they go into a queue. When there are sufficient CAVA servers, and the servers are lightly loaded, the queue stays (relatively) small. If the number of scanning requests increase or the time to scan each file increases, the queue can get quite large. By default, CAVA will post a LOW watermark message when the number of files waiting to be scanned exceeds 50, and will post a HIGH watermark message when the number of files waiting to be scanned exceeds 200.
Assuming there are no major issues with the Celerra, the simplest solution is to add more CAVA servers to the pool (it's pretty easy to do, and can be done "live", without stopping/restarting CAVA). Or, you can exclude more filetypes, reducing the scan load.
If you often see HIGH watermark messages, it's usually sign that there are not enough CAVA servers, or something is preventing the CAVA servers from doing real work (maybe virus DAT updates are happening too frequently, or are happening on all the CAVA servers at the same time?)