[GH-ISSUE #42] Install issue on proxmox lxc #41

Closed
opened 2026-02-27 15:54:38 +03:00 by kerem · 3 comments
Owner

Originally created by @tscibilia on GitHub (Jun 19, 2017).
Original GitHub issue: https://github.com/RD17/ambar/issues/42

The install process was easy and straightforward. I was excited to get started with ambar, but at the very end I received a message in the console

sysctl: cannot stat /proc/sys/net/ipv4/tcp_fin_timeout: No such file or directory

I know lxc containers have an issue running docker (which I was able to get around by modifying the lxc conf file to include some extra parameters. I realize this is probably not the safest practice but the container would only be accessible on a local network. Since I'm still having issues with the container I was hoping to see if anyone had a solution I missed.

Originally created by @tscibilia on GitHub (Jun 19, 2017). Original GitHub issue: https://github.com/RD17/ambar/issues/42 The install process was easy and straightforward. I was excited to get started with ambar, but at the very end I received a message in the console `sysctl: cannot stat /proc/sys/net/ipv4/tcp_fin_timeout: No such file or directory` I know lxc containers have an issue running docker (which I was able to get around by modifying the lxc conf file to include some [extra parameters](http://ashish1099.github.io/blog/2015/05/23/docker-inside-lxc/). I realize this is probably not the safest practice but the container would only be accessible on a local network. Since I'm still having issues with the container I was hoping to see if anyone had a solution I missed.
kerem 2026-02-27 15:54:38 +03:00
Author
Owner

@sochix commented on GitHub (Jun 19, 2017):

Hello @tscibilia ! This line sysctl -w net.ipv4.tcp_fin_timeout=30 was added to tune Ubuntu tcp/ip stack, I think in your case just comment it out in your ambar.py file:

# runShellCommandStrict('sysctl -w net.ipv4.tcp_fin_timeout=30')
<!-- gh-comment-id:309457186 --> @sochix commented on GitHub (Jun 19, 2017): Hello @tscibilia ! This line `sysctl -w net.ipv4.tcp_fin_timeout=30 ` was added to tune Ubuntu tcp/ip stack, I think in your case just comment it out in your `ambar.py` file: ``` # runShellCommandStrict('sysctl -w net.ipv4.tcp_fin_timeout=30') ```
Author
Owner

@tscibilia commented on GitHub (Jun 19, 2017):

thanks that worked, except i had to comment out a few other errors.

# runShellCommandStrict('sysctl -w net.ipv4.tcp_fin_timeout=30')

# runShellCommandStrict('sysctl -w net.core.netdev_max_backlog=2000')
# runShellCommandStrict('sysctl -w net.ipv4.tcp_max_syn_backlog=2048')

<!-- gh-comment-id:309500621 --> @tscibilia commented on GitHub (Jun 19, 2017): thanks that worked, except i had to comment out a few other errors. `# runShellCommandStrict('sysctl -w net.ipv4.tcp_fin_timeout=30')` `# runShellCommandStrict('sysctl -w net.core.netdev_max_backlog=2000')` `# runShellCommandStrict('sysctl -w net.ipv4.tcp_max_syn_backlog=2048')`
Author
Owner

@sochix commented on GitHub (Jun 20, 2017):

Nice!

<!-- gh-comment-id:309740741 --> @sochix commented on GitHub (Jun 20, 2017): Nice!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ambar#41
No description provided.