View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
1947 | RackTables | default | public | 2019-12-05 20:28 | 2020-01-16 23:30 |
Reporter | jluo | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | unable to reproduce | ||
Product Version | 0.21.3 | ||||
Summary | 1947: Object Port not loading | ||||
Description | If there is at least 60 ports on an object if the page would not load or would not show all the ports. | ||||
Steps To Reproduce | Used the multi port port creator and made 60 sftp+ ports. Then tried to refresh, reload, leave and come back. | ||||
Additional Information | MySQL has the ports not shown in it's system as trying to create a port of the same name will error out saying that there is a port of the same name. | ||||
Tags | No tags attached. | ||||
|
|
Does the problem reproduce on demo.racktables.org? | |
It does not reproduce on demo.racktables.org | |
If you check the page source, does the generated HTML end abruptly or contain any invalid characters or error messages? Are there any PHP errors/warnings in the server error log? | |
There is no browser error in Edge but there is an error in Chrome. GET "Object URL" net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 (OK) This error pops up in the error log file when both edge and chrome try to load the page. 2019/12/13 13:32:09 [crit] 32#32: *1431 open() "/var/tmp/nginx/fastcgi/7/03/0000000037" failed (13: Permission denied) while reading upstream, client: 172.16.19.14, server: localhost, request: "GET /index.php?page=object&tab=ports&object_id=123 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "IP Address" |
|
It looks more like a nginx/FastCGI configuration issue rather than a RackTables bug. I do not have much experience in this area, but I would guess there is a data buffer between nginx and PHP, and one of the components is not properly writing to it or the other isn't properly reading from it, or even both. For example, the two ends could have different assumptions about the default buffer size, but the HTTP response needs to be of a specific size to make the problem visible. Hopefully this provides enough direction for you to investigate the server configuration closer. | |
From the comments above I have to conclude most likely this is either a server misconfiguration or a bug in some other software, hence closing. Feel free to reopen if you can prove the problem belongs to RackTables. | |
Date Modified | Username | Field | Change |
---|---|---|---|
2019-12-05 20:28 | jluo | New Issue | |
2019-12-05 20:28 | jluo | File Added: Capture.PNG | |
2019-12-05 22:39 | infrastation | Note Added: 0004025 | |
2019-12-12 18:13 | jluo | Note Added: 0004033 | |
2019-12-12 20:14 | infrastation | Note Added: 0004035 | |
2019-12-13 14:34 | jluo | Note Added: 0004037 | |
2019-12-13 15:16 | infrastation | Note Added: 0004039 | |
2020-01-16 23:30 | infrastation | Status | new => closed |
2020-01-16 23:30 | infrastation | Resolution | open => unable to reproduce |
2020-01-16 23:30 | infrastation | Note Added: 0004041 |