-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creation of sapuc standard filebuf failed #356
Comments
need some more info
|
Hi there, I have the same problem. About one third of our pyrfc requests fail, so I traced them with strace and it seems to be a problem with the file descriptor:
If the request fails, the file descriptor in the first part is always 0. In the successfull requests, the file descriptor is 3:
I followed the trace to the source of the file descriptor number and it seems to be determined by opening the /etc/ld.so.cache:
Success:
|
@MisterGG could you please crate new issue, describe PyRFC usage scenario and steps to reproduce |
Same issue when calling a python script as ExternalScript from Zabbix server When the RFc call is working I have this trace : I found a workaround by calling the python script with stdin redirection to force FD 0 creation |
Describe the big
SAP RFC calls from the Foresight platform scheduler do not work. The error "Creation of sapuc standard filebuf filed." occurs, the scheduler restarts.
The problem only occurs on Linux, there is no such problem on Windows. Is it possible that the problem is on the library side?
To Reproduce
Run any python script from the scheduler (not manually, but by a scheduled process):
Environment
**Additional content
The text was updated successfully, but these errors were encountered: