Created
July 22, 2018 03:19
-
-
Save ngoquang2708/190e863a7a2700459028e92102bf1ef5 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
07-22 03:08:42.833 134 169 W IptablesRestoreController: iptables-restore process 139 terminated status=256 | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: iptables error: | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: ------- COMMAND ------- | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: *filter | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: -A st_penalty_log -j CONNMARK --or-mark 0x1000000 | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: -A st_penalty_log -j NFLOG --nflog-group 0 | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: -A st_penalty_reject -j CONNMARK --or-mark 0x2000000 | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: -A st_penalty_reject -j NFLOG --nflog-group 0 | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: -A st_penalty_reject -j REJECT | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: -A st_clear_detect -m connmark --mark 0x2000000/0x2000000 -j REJECT | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: -A st_clear_detect -m connmark --mark 0x1000000/0x1000000 -j RETURN | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: -A st_clear_detect -p tcp -m u32 --u32 "0>>22&0x3C@ 12>>26&0x3C@ 0&0xFFFF0000=0x16030000 &&0>>22&0x3C@ 12>>26&0x3C@ 4&0x00FF0000=0x00010000" -j CONNMARK --or-mark 0x1000000 | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: -A st_clear_detect -p udp -m u32 --u32 "0>>22&0x3C@ 8&0xFFFF0000=0x16FE0000 &&0>>22&0x3C@ 20&0x00FF0000=0x00010000" -j CONNMARK --or-mark 0x1000000 | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: -A st_clear_detect -m connmark --mark 0x1000000/0x1000000 -j RETURN | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: -A st_clear_detect -p tcp -m state --state ESTABLISHED -m u32 --u32 "0>>22&0x3C@ 12>>26&0x3C@ 0&0x0=0x0" -j st_clear_caught | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: -A st_clear_detect -p udp -j st_clear_caught | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: COMMIT | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: ------- ERROR ------- | |
07-22 03:08:42.833 134 169 E IptablesRestoreController: iptables-restore: line 246 | |
07-22 03:08:42.876 134 169 W IptablesRestoreController: iptables-restore process 140 terminated status=256 | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: iptables error: | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: ------- COMMAND ------- | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: *filter | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: -A st_penalty_log -j CONNMARK --or-mark 0x1000000 | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: -A st_penalty_log -j NFLOG --nflog-group 0 | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: -A st_penalty_reject -j CONNMARK --or-mark 0x2000000 | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: -A st_penalty_reject -j NFLOG --nflog-group 0 | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: -A st_penalty_reject -j REJECT | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: -A st_clear_detect -m connmark --mark 0x2000000/0x2000000 -j REJECT | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: -A st_clear_detect -m connmark --mark 0x1000000/0x1000000 -j RETURN | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: -A st_clear_detect -p tcp -m u32 --u32 "52>>26&0x3C@ 40&0xFFFF0000=0x16030000 &&52>>26&0x3C@ 44&0x00FF0000=0x00010000" -j CONNMARK --or-mark 0x1000000 | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: -A st_clear_detect -p udp -m u32 --u32 "48&0xFFFF0000=0x16FE0000 &&60&0x00FF0000=0x00010000" -j CONNMARK --or-mark 0x1000000 | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: -A st_clear_detect -m connmark --mark 0x1000000/0x1000000 -j RETURN | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: -A st_clear_detect -p tcp -m state --state ESTABLISHED -m u32 --u32 "52>>26&0x3C@ 40&0x0=0x0" -j st_clear_caught | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: -A st_clear_detect -p udp -j st_clear_caught | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: COMMIT | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: ------- ERROR ------- | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: ip6tables-restore: line 227 failed | |
07-22 03:08:42.876 134 169 E IptablesRestoreController: ---------------------- | |
07-22 03:08:42.885 334 334 E NetworkManagement: Failed strict enable | |
07-22 03:08:42.885 334 334 E NetworkManagement: com.android.server.NativeDaemonConnector$NativeDaemonFailureException: command '7 strict enable' failed with '400 7 Strict command failed' | |
07-22 03:08:42.885 334 334 E NetworkManagement: at com.android.server.NativeDaemonConnector.executeForList(NativeDaemonConnector.java:505) | |
07-22 03:08:42.885 334 334 E NetworkManagement: at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:401) | |
07-22 03:08:42.885 334 334 E NetworkManagement: at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:396) | |
07-22 03:08:42.885 334 334 E NetworkManagement: at com.android.server.NetworkManagementService.prepareNativeDaemon(NetworkManagementService.java:654) | |
07-22 03:08:42.885 334 334 E NetworkManagement: at com.android.server.NetworkManagementService.systemReady(NetworkManagementService.java:402) | |
07-22 03:08:42.885 334 334 E NetworkManagement: at com.android.server.SystemServer.lambda$-com_android_server_SystemServer_78011(SystemServer.java:1775) | |
07-22 03:08:42.885 334 334 E NetworkManagement: at com.android.server.-$Lambda$T7cKu_OKm_Fk2kBNthmo_uUJTSo$1.$m$0(Unknown Source:98) | |
07-22 03:08:42.885 334 334 E NetworkManagement: at com.android.server.-$Lambda$T7cKu_OKm_Fk2kBNthmo_uUJTSo$1.run(Unknown Source:0) | |
07-22 03:08:42.885 334 334 E NetworkManagement: at com.android.server.am.ActivityManagerService.systemReady(ActivityManagerService.java:14326) | |
07-22 03:08:42.885 334 334 E NetworkManagement: at com.android.server.SystemServer.startOtherServices(SystemServer.java:1722) | |
07-22 03:08:42.885 334 334 E NetworkManagement: at com.android.server.SystemServer.run(SystemServer.java:411) | |
07-22 03:08:42.885 334 334 E NetworkManagement: at com.android.server.SystemServer.main(SystemServer.java:274) | |
07-22 03:08:42.885 334 334 E NetworkManagement: at java.lang.reflect.Method.invoke(Native Method) | |
07-22 03:08:42.885 334 334 E NetworkManagement: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440) | |
07-22 03:08:42.885 334 334 E NetworkManagement: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:787) | |
07-22 03:08:42.958 334 334 W NetworkManagement: setDataSaverMode(): already false |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment