joorschot Absent Member.
Absent Member.
2118 views

Empty message log ((upload would exceed size limit)

Our message logs on devices and bundles are empty. (ZCM 11.2.4)
Searching the logs i found:
[MESSAGELOGGER.Debug] [31-3-14 12:14:13] [] [File Upload Servlet] [159762] [] [Recalculating 'C:\Program Files (x86)\Novell\ZENworks\work\collection' directory size.] [] []
[MESSAGELOGGER.Debug] [31-3-14 12:14:13] [] [File Upload Servlet] [29] [] [Upload would exceed size limit. status file : Status_c3f05b9d9861ba44b79dc7d83b59804b_1396260853625.zip] [] []

The Collection folder on our ZCM server is 10G and the ..\collection\inventory folder contains about 30000 old xml files adding up to 10G.
Failed and Success folders are empty.
how can I clean up the folder (is it as simple as deleting the files)?

John
Labels (2)
0 Likes
14 Replies
shaunpond Absent Member.
Absent Member.

Re: Empty message log ((upload would exceed size limit)

Joorschot,

i think finding out why they're not being auto-deleted would be a
start... look in loader-messages for references

--

Shaun Pond
newly reminted as a Knowledge Professional


0 Likes
joorschot Absent Member.
Absent Member.

Re: Empty message log ((upload would exceed size limit)

Shaun,

Thanx for your reply.

The loader-messages log has entries from feb 26th till now.
The XML files in the Inventory folder are from nov 2011 till sept 2013.
Should I still see some logging regarding why it's not auto-deleting the files?


John
0 Likes
shaunpond Absent Member.
Absent Member.

Re: Empty message log ((upload would exceed size limit)

Joorschot,

the loader-messages shows when it's trying to process the files, so
search for Loader.InventoryStorerAMModule

--

Shaun Pond
newly reminted as a Knowledge Professional


0 Likes
joorschot Absent Member.
Absent Member.

Re: Empty message log ((upload would exceed size limit)

Shaun,

I see it only 1 time in the log:

MESSAGELOGGER.Debug] [14-3-14 21:18:33] [] [Loader.InventoryStorerAMModule] [60] [] [InventoryStorerModule: Running...] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:33] [] [Loader.Collection Rollup] [41] [] [CollectionRollup, no parent, so no rollup on this server.] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:33] [] [iAMTDiscoveryModule] [30] [] [Waiting for incoming connections at 9971....] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:34] [] [Loader.ApplyPruAMModule] [37] [] [Initial PRU is NOT needed] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:34] [] [Loader.ComplianceEngine] [42] [] [ Number of Licensed Products: 0] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:49] [] [Loader.ComplianceEngine] [42] [] [Refresh all complete] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:49] [] [Loader.ComplianceEngine] [42] [] [Refreshing user source data: Inventory] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:49] [] [Loader.ComplianceEngine] [42] [] [Refreshing user source complete] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:49] [] [Loader.CasaAuthRealmConfigurator] [39] [] [CasaAuthRealmConfigurator initialized.] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:49] [] [Location.Configuration] [71] [] [Beginning location response computation ZENObject : f94d61cd4c62969ff6b65fb71de050d5] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:49] [] [Location.Configuration] [71] [] [Location last modified has not changed, not computing location response for ZENObject = f94d61cd4c62969ff6b65fb71de050d5] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:49] [] [Location.Configuration] [71] [] [Finished location computation in (ms): 16for ZENObject : f94d61cd4c62969ff6b65fb71de050d5] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:49] [] [Location.Configuration] [71] [] [Beginning location configuration computation for ZENObject : f94d61cd4c62969ff6b65fb71de050d5] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:50] [] [Location.Configuration] [71] [] [Sucessfully updated Location Configuration Response for ZENObject : f94d61cd4c62969ff6b65fb71de050d5] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:50] [] [Location.Configuration] [71] [] [Finished location configuration computation in (ms): 687for ZENObject : f94d61cd4c62969ff6b65fb71de050d5] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:18:50] [] [Location.Configuration.Module] [71] [] [Successfully computed location responses] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:20:04] [] [Loader.Status Storer Module] [83] [] [Processing Status_6c7a09aa78aa3f489d02b371b50477f8_1394824581577.xml] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:20:04] [] [TransferFileFTPSettingsToBO] [23] [] [File & FTP notification settings loader module is not loaded as this is not a reporting server] [] []
[MESSAGELOGGER.Debug] [14-3-14 21:20:04] [] [TransferSMTPSettings] [93] [] [SMTP & EMAIL notification settings loader module is not loaded as this is not a reporting server] [] []


John
0 Likes
shaunpond Absent Member.
Absent Member.

Re: Empty message log ((upload would exceed size limit)

Joorschot,

hmm... and nothing in the zipped-up old files? If there are no clues,
and it's been a while since your server was last restarted, I would
restart the zenworks server service

--

Shaun Pond
newly reminted as a Knowledge Professional


0 Likes
joorschot Absent Member.
Absent Member.

Re: Empty message log ((upload would exceed size limit)

Shaun,

No extra information in the zipped log files.
We've got 3 primary servers with the same problem.
All stopped on the sept 19th of last year. (reached 10G).
Restart of Zenworks server service (tested on 1 server)didn't clean up the folder.

All the servers were restarted in januari after our update to 11.2.4.

We should have seen this before but there was no need for troubleshooting bundles so we didn't see it. 😮

Is there something I should check in ZCC, because it's on all 3 servers?

John
0 Likes
shaunpond Absent Member.
Absent Member.

Re: Empty message log ((upload would exceed size limit)

Joorschot,

> No extra information


you mean that there's only the same message in each? I would get the
zdc http://download.novell.com/Download?buildid=nffCG6SwnTc~ and check
your zone as a first step. If that doesn't show any problems, then I
think a Service Request is necessary

--

Shaun Pond
newly reminted as a Knowledge Professional


0 Likes
joorschot Absent Member.
Absent Member.

Re: Empty message log ((upload would exceed size limit)

Shaun,

Yes, the same information\message in each.

Do you know if there is a baselinefile for 11.2.4 mu1?

John
0 Likes
joorschot Absent Member.
Absent Member.

Re: Empty message log ((upload would exceed size limit)

Shaun,

Yes, the same information.

Do you know if there is a baselinefile for 11.2.4 mu1?

John
0 Likes
shaunpond Absent Member.
Absent Member.

Re: Empty message log ((upload would exceed size limit)

Joorschot,

no, not for MU1, it takes too long to generate and test, to be able to
do it for an MU unfortunately.

--

Shaun Pond
newly reminted as a Knowledge Professional


0 Likes
joorschot Absent Member.
Absent Member.

Re: Empty message log ((upload would exceed size limit)

Shaun,

Ok.
Got a lot of errors on file versions, but those we're a lot of mu1 files.
I will check them manually.
Did get dbase error also but don't know if this also has to do with mu1.

I will make a SR.
Thanx for your quick and helpfull replies.

John
0 Likes
shaunpond Absent Member.
Absent Member.

Re: Empty message log ((upload would exceed size limit)

Joorschot,

hope they get you working ASAP

--

Shaun Pond
newly reminted as a Knowledge Professional


0 Likes
joorschot Absent Member.
Absent Member.

Re: Empty message log ((upload would exceed size limit)

Shaun,

I't's working.
Novell support advised me to delete the XML files.
And to start a inventory on a machine (zac inv scannow), delta file was created and sent to the server.
Delta arrived at the server, but didn't process.
I remembered your suggestion to restart the Zeworks service.
This time I only restarted the Loader service and the files were processed.

Thanks again.
John
0 Likes
shaunpond Absent Member.
Absent Member.

Re: Empty message log ((upload would exceed size limit)

Joorschot,

nice!

--

Shaun Pond
newly reminted as a Knowledge Professional


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.