mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1520] Firejail MySQL #1016
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1016
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cjconstante on GitHub (Sep 3, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1520
Hi. I have been trying to run MySQL for a jailed web server with fireajil. When i try to start the jail, it can not start because i changed the bind-address to 10.10.X.X segment. It only runs on 127.0.0.1 bind-address.
This says the log:
Sep 1 08:05:43 debian78 mysqld: 32:mysqld_safe:open /dev/null:2
Sep 1 08:05:43 debian78 mysqld: /usr/bin/mysqld_safe: line 229: 3306: command not found
Sep 1 08:05:43 debian78 mysqld_safe: mysqld from pid file 101:sed:fopen64 /proc/filesystems:0x25b9040#012101:sed:open //lib/charset.alias:-1#012/var/lib/mysql/89:sed:fopen64 /proc/filesystems:0x186d040#01289:sed:open //lib/charset.alias:-1#012/var/run/mysqld/mysqld.pid ended
Sep 1 08:05:56 debian78 kernel: [11735.262445] br0: port 1(veth5583eth0) entered forwarding state
Sep 1 08:06:12 debian78 /etc/init.d/mysql[565]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Sep 1 08:06:12 debian78 /etc/init.d/mysql[565]: 557:mysqladmin:fopen /etc/services:0x289a300
Sep 1 08:06:12 debian78 /etc/init.d/mysql[565]: 557:mysqladmin:fopen64 /etc/mysql/debian.cnf:0x289a510
Sep 1 08:06:12 debian78 /etc/init.d/mysql[565]: 557:mysqladmin:socket AF_INET SOCK_STREAM IPPROTO_TCP:4
Sep 1 08:06:12 debian78 /etc/init.d/mysql[565]: 557:mysqladmin:connect 4 10.10.20.20 port 3306:-1
Sep 1 08:06:12 debian78 /etc/init.d/mysql[565]: #007/usr/bin/mysqladmin: connect to server at '10.10.20.20' failed
Sep 1 08:06:12 debian78 /etc/init.d/mysql[565]: error: 'Can't connect to MySQL server on '10.10.20.20' (111 "Connection refused")'
Sep 1 08:06:12 debian78 /etc/init.d/mysql[565]: Check that mysqld is running on 10.10.20.20 and that the port is 3306.
Sep 1 08:06:12 debian78 /etc/init.d/mysql[565]: You can check this by doing 'telnet 10.10.20.20 3306'
Sep 1 08:06:12 debian78 /etc/init.d/mysql[565]:
How i can fix this?
@SkewedZeppelin commented on GitHub (Sep 3, 2017):
What profile are you using? What version of Firejail are you running? And what is the command you're using to start it? Are you using a separate network namespace?
@cjconstante commented on GitHub (Sep 3, 2017):
Thanks for reply.
firejail version 0.9.50~rc2. I have tried with previous version and from debian testing repository.
With and without profile i get the same.
This is the command:
firejail --profile=/usr/local/etc/firejail/mysql.profile --private --net=br0 --ip=10.10.20.20 /etc/init.d/mysql start; sleep inf &
I have this in the profile:
@chiraag-nataraj commented on GitHub (Aug 23, 2018):
@cjconstante Is this still an issue?
@cjconstante commented on GitHub (Aug 23, 2018):
@chiraag-nataraj I don't remember exactly because this was a year ago. I think i disabled the private and net flags and then i enabled the admin, net and write flags in the command to run it.
@chiraag-nataraj commented on GitHub (Aug 23, 2018):
Mmkay. If you don't have the issue anymore, let's go ahead and close this. Feel free to reopen if you run into the issue again.