|
|
Rank: Newbie
Groups: Member
Joined: 3/17/2023
Posts: 2
|
Hello,
Reading this forum I always see send the logs to us, is it true that only you can decode that log message?
This child process error keeps happening no matter the versions we are using, hard to debug, no information is provided of why it failed;
Usage of EO is very simple just giving it a string of html and a memory stream;
HtmlToPdf.ConvertHtml(template, stream);
we are using it on microsoft azure, anything known about azure settings that might cause these issues?
we currently moved the product to its own server farm, it has dedicated 8 gb of ram and 4 cpus on its own, resources cannot be a problem, we generate a pdf every 10 minutes or so;
Another detail that might be interesting that this is running as background task
await _backgroundTaskQueue.QueueBackgroundWorkItemAsync()
any clues how to proceed finding the problem?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,080
|
Hi,
Yes. It is correct that only we can decode the logs. The logs are sometimes very specific to a particular problem and it contains information that only makes sense to us. For hard to troubleshoot issue like this, what we do is analyze the log to see where the problem might be, then add more logs to the suspected area, run it and collect the new log, analyze it again to narrow down the scope, add more logs, run it again, over and over again until we get to the bottom of the problem. So the log is never meant for the end user to make any changes on their end, it is meant to provide more information for us to make code changes on our end.
We did discover and fix one issue that can cause the child process error this month while we were working with another customer. The fix is in the new build we just posted yesterday. So please download that build and see if it resolves the issue for you. If it still does not work, please collect the logs through EO.Base.Runtime.GetLogs() and send it to us. We will look into the log and send you test build with more logs, then over and over again until we get to the bottom of it.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 3/17/2023
Posts: 2
|
well,
we did upgrade to newest 23.1.45 and got the child process crash again;
tried to write with
EO.Base.Runtime.WriteLog(EO.Base.Runtime.GetLogs());
but that caused out of memory exception, any tips to proceed?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,080
|
Hi,
This is just to let you know we did see something wrong in the log files you sent to us. However we are still not able to determine the root cause it. We may need to add additional log entries and send you a test build in order to collect more information. We will reply here again once we have the new test build ready for you.
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,080
|
Hi,
We have sent a new build to you through your email. We did find and fix an issue in the new build. However we are still not sure if there are other problems. So please try to the new build and collect the logs again.
Thanks!
|
|