Smartview Logs Export Takes Too Long

[DominusRex23]

Hi CheckMates,

We're currently running a standalone 3600 appliance on R82 (no hotfixes applied yet). When accessing SmartView, we're consistently seeing a "Query Failed" error. Additionally, log exports are extremely slow—even for a small set of ~1K logs, the export process is still stuck in "Generating" as of this writing.

Has anyone encountered similar behavior on R82?
Is this something that requires a specific hotfix, or could we be missing a configuration step?

Appreciate any insights or suggestions!

[the_rock]

Installing recommended jumbo would not hurt, but, how much ram does appliance have?

Andy

[Amir_Senn]

I would check processes with "cpwd_admin list" on the machine and check if log related processes are working properly.

You can also try "evstop ; evstart" to stop and start log related processes and see if this solves the issue.

JHF is always recommended and it will restart processes as well.

[the_rock]

Great points Amir.

[victorjaou]

Hello, 

I am in the same situation on virtual machine smartconsole running R82 JHF60. I need to export a full week of logs filtered by a single IP address, which arounds 800,000 entries. The task was running for two hours, and I stopped it because it was impacting other searches in SmartView. I do not seem to be able to export anything close to one million log entries.

[Expert@smc:0]# cpwd_admin list
APP PID STAT #START START_TIME MON COMMAND
CPVIEWD 14077 E 1 [12:19:56] 11/2/2026 N cpviewd
CPOTELCOL 19066 E 1 [11:33:41] 23/2/2026 N otlpcol
OTLPAGENT 14168 E 1 [12:19:56] 11/2/2026 N cpview_exporter
OTLPAGENTDEMON 14181 E 1 [12:19:57] 11/2/2026 N otlp_agent
CVIEWAPIS 14197 E 1 [12:19:57] 11/2/2026 N cpview_api_service
CPVIEWS 11262 E 1 [12:33:29] 11/2/2026 N cpview_services
MSGD 14248 E 1 [12:19:57] 11/2/2026 Y msgd
CPD 14348 E 1 [12:19:57] 11/2/2026 Y cpd
FWD 14417 E 1 [12:19:57] 11/2/2026 N fwd -n
FWM 14424 E 1 [12:19:57] 11/2/2026 N fwm
FWMHA 14430 E 1 [12:19:57] 11/2/2026 N fwmha -H
STPR 14460 E 1 [12:19:58] 11/2/2026 N status_proxy
CLOUDGUARD 16988 E 1 [15:21:09] 11/2/2026 N vsec_controller_start
CPM 14960 E 1 [12:19:59] 11/2/2026 N /opt/CPsuite-R82/fw1/scripts/cpm.sh -s
SOLR 6147 E 1 [11:55:50] 24/2/2026 N java_solr
RFL 20817 E 2 [14:22:10] 24/2/2026 N LogCore
SMARTVIEW 12852 E 1 [10:46:25] 24/2/2026 N SmartView
INDEXER 15530 E 1 [12:20:01] 11/2/2026 N /opt/CPrt-R82/log_indexer/log_indexer -workingDir /opt/CPrt-R82/log_indexer/
SMARTLOG_SERVER 15695 E 1 [12:20:02] 11/2/2026 N /opt/CPSmartLog-R82/smartlog_server
AUTOUPDATER 17086 E 1 [12:20:06] 11/2/2026 N AutoUpdaterService.sh
EXPORTER.srvlelk03ap.cfl.lu 28259 E 1 [12:27:49] 11/2/2026 N /opt/CPrt-
CPSEMD 17824 E 1 [12:20:12] 11/2/2026 Y cpsemd
CPSEAD 17832 E 1 [12:20:12] 11/2/2026 N cpsead
REPMAN 17845 E 1 [12:20:13] 11/2/2026 N java_repository_manager
DASERVICE 17856 E 1 [12:20:13] 11/2/2026 N DAService_script
CPSM 7241 E 1 [12:22:46] 11/2/2026 N cpstat_monitor
LPD 20766 E 1 [02:08:54] 23/2/2026 N lpd

Do you advise avoid using SmartView for this amount of log ? 

Best regards,

[Amir_Senn]

Hi,

SmartView supports up to 1 million logs.

You can try to export only visible fields if that helps.

[Lesley · Accepted solution]

Check this one out, solved in take 73:

PRJ-64465, PRHF-42386

Logging

In some scenarios, exporting logs to CSV in SmartView fails and the LOG_INDEXER process unexpectedly exits. Refer to sk184475.

I assume you export to CSV. How is the CPU load during an export? Many factors can go wrong here, wrong sizing , incorrect configuration out of the box. Anything useful in health check report (hcp -r all) Some exports can take couple hours depending on many factors. 

[victorjaou]

Hello, 

I upgraded the smc to R82 JHF73 and tested again. I was able to export a week full in 10 mins. I chose "only visible columns" and All logs. In JHF60 the CPU was topping with the exporter task. 

Thank for the answers,