| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Trying to send a WakeOnLan command to 150 clients I noticed that the
ogAdmClient closed (RST) the communication with the WebConsole without
answering or logging anything. The Webconsole logged:
php: error occured during curl exec. Additioanl info: Array
php: (
php: [url] => http://127.0.0.1:8888/wol
php: [content_type] =>
php: [http_code] => 0
php: [header_size] => 0
php: [request_size] => 199
php: [filetime] => -1
php: [ssl_verify_result] => 0
php: [redirect_count] => 0
php: [total_time] => 1.003122
php: [namelookup_time] => 4.9E-5
php: [connect_time] => 0.000273
php: [pretransfer_time] => 0.00035
php: [size_upload] => 7007
php: [size_download] => 0
php: [speed_download] => 0
php: [speed_upload] => 6986
php: [download_content_length] => -1
php: [upload_content_length] => 7007
php: [starttransfer_time] => 1.001793
php: [redirect_time] => 0
php: [redirect_url] =>
php: [primary_ip] => 127.0.0.1
php: [certinfo] => Array
php: (
php: )
php:
php: [primary_port] => 8888
php: [local_ip] => 127.0.0.1
php: [local_port] => 43016
php: [http_version] => 0
php: [protocol] => 1
php: [ssl_verifyresult] => 0
php: [scheme] => HTTP
php: )
This happened because request max length is set to 4096 bytes and my
request had a size of 7075 bytes. So, the max length was exceeded.
This commit increase the max length from 4096 to 16384. This way the
ogAdmServer supports larger request messages.
|
|
|
|
| |
Missing dbi_result_free(), use syslog() for logging.
|
|
|
|
|
|
| |
This patch fixes e052fdceec013 that adds a missing error in case
the insertion fails. This also releases the result in case the
entry exists.
|
|
|
|
| |
This is fixing e052fdceec013 that releases the libdbi result twice.
|
|
|
|
| |
These have been replaced by the new REST API.
|
|
|
|
| |
This patch ensures that some variables are initialized before using them.
|
|
|
|
| |
This actually is C code, use the gcc compiler instead.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
And update all callers.
Some of the db.Open() calls cannot be removed yet, since there are still
more function dependencies that need to be converted too.
|
|
|
|
|
|
| |
RestaurarSoftIncremental, Configurar and EjecutarScript
These functions are identical, remove duplicated code.
|
|
|
|
|
|
| |
RESPUESTA_Apagar
They are identical, remove duplicated code.
|
|
|
|
| |
These function are almost identical, remove duplicated code.
|
| |
|
| |
|
| |
|
|
|
|
| |
Add basic infrastructure to support for the independent database layer.
|
|
|
|
|
|
|
|
|
|
|
| |
Irina reports that the bug fixed in 78a97c5 happens again when you run a
command with a session (queue of actions).
The bug was introduced in 78a97c5, the goal of the commit was
to change the behaviour of respuestaEstandar to always check
the result of a command, whether it has a session or not. But, instead
of this behaviour, the commit changes respuestaEstandar to only check the
commands without session.
|
|
|
|
| |
configuration.
|
|
|
|
|
| |
This patch meets RFC 7235 and returns an HTTP 400 error code when ogAdmServer
recieves a wrong request.
|
|
|
|
| |
This patch renames the setup command to avoid semantic confusion.
|
|
|
|
| |
'echo' parameter makes possible for users to request the console output.
|
|
|
|
|
| |
This patch prevents the flag OG_REST_PARAM_ADDR to be activated when the array
is empty.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
hide/unhide NTFS partitions.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
| |
This patch ensures that all required parameters are sent in the request.
|
|
|
|
|
|
|
| |
This patch adds og_msg_params_validate function as well as some flags that can
be used to validate parameters of a REST API request.
This patch ensures that all required parameters are sent in the request.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Irina reports that if you try to restore an image without success
(for example: the disk does not have enough space), the database changes
as if no error would happen. So you see the computer in the WebConsole
with an image/OS that, actually, does not have.
The bug is caused because the function respuestaEstandar only checks
the result of a command if it has a session. So the problem is that the
commands which use respuestaEstandar without a session can return an
error, but the ogAdmServer always works as no error would occur.
This commit changes the behaviour of respuestaEstadar to always check
the result of a command, whether it has a session or not.
|
|
|
|
|
| |
This patch simplifies the og_cmd_run_schedule function by calling
og_cmd_legacy_send.
|