Hello M. BM,
Unfortunately you cannot change this as it is hardcoded in the GUI. The only 3 possibilities to workaround this 1GB issue are:
1. Reducing the timeframe of the query and run multiple query/extract on the GUI (time consuming)
2. Using the script I made, which automate this process (don't forget to use a screen session to avoid timeout)
3. Using the SFTP interface provided with the ELM. The drawback is that you will have to filter the raw data to extract the desired information
Let me know if it answers your question
Did not face this error yet, however it seems related to the storage pools.
Did you already check the available space left per storage pool in the ELM Properties > Storage Pools.
There is no problem with storage.
Actually the problem occurred during the search on ELM and It is occurring when there are a lot of result.
I think there is a problem with catching result or some limitation it has!
Any Idea can be helpful.
With the few detailed you gave, I was able to reproduce your issue.
I can confirm that it is related to both discussions I mentionned in my previous post and that even you are in the "Enhanced ELM search" view, you hit the 1GB limit and causing this error.
@nickram: I was able to reproduce the issue and confirm that it is not storage related.
When you do a search on the ELM using the ESM, there is a limit on the size you can query which is 1GB. Also the GUI does not accept any values bigger then 1GB.
The reason behind, is that the system is launching a command in the background elmsearch which required this optional parameter:
g = Optional. The maximum number of MB of output allowed. When the number of result bytes plus the number of bytes in all files saved in 'kd' reach this amount the program will terminate. If this value is not specified no output constraint will be imposed. Note that there is an internal limit of 2GB on the number of result bytes.
Note: When I did some testing developping the script I have mention previously, it apparently does not accept any values over 1GB.
The error that M. BM is actually seeing is directly related to that because he is querying a large amount of data, which can not be achieved using the GUI unfortunately.
@M. BM: do you have some feedback already?