mhlnstdt25
Members-
Posts
10 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
mhlnstdt25's Achievements
Noob (1/14)
0
Reputation
-
No that is not the error, i added after the server crashing and the log suggested to add -debug to get more information. I will add a log without -debug from 6.8 gmod_2.log
-
It worked in unraid 6.7 I added the following parameter for TTT. I removed the webapikey and collection_id. Also a collection with a lot of mods. -secure +gamemode terrortown +maxplayers 16 +map gm_construct -authkey {steam_web_api_key} +host_workshop_collection {collection_id} -debug I rolled back to 6.7. If you need more info i can (re-)upgrade to 6.8 gmod.log
-
mhlnstdt25 started following 6.6.7 Gui Freeze, shares drop, telnet up for a little after than it dies too. , [Support] ich777 - Gameserver Dockers , [Support] Rocket.Chat and 3 others
-
Running in Unraid 6.8.0_rc.3 i get the following error message when using the gmod server with -debug: Using default binary: ./srcds_linux Enabling debug mode /serverdata/serverfiles/srcds_run: 182: ulimit: error setting limit (Operation not permitted) /serverdata/serverfiles/srcds_run: 1: /serverdata/serverfiles/srcds_run: gdb: not found WARNING: Please install gdb first. goto http://www.gnu.org/software/gdb/ Server will auto-restart if there is a crash. ---Server ready--- The server doesn't start
-
Access Control is only a warning, you can ignore that. Maybe try mongo-express to check if your mongodb is running Also the rocket chat startup does take a few minutes. When u see something like this, the rocketchat instance should be reachable. [32m➔[39m [32mSystem ➔ startup[39m [32m➔[39m [32m+---------------------------------------------+[39m [32m➔[39m [32m| SERVER RUNNING |[39m [32m➔[39m [32m+---------------------------------------------+[39m [32m➔[39m [32m| |[39m [32m➔[39m [32m| Rocket.Chat Version: 1.2.1 |[39m [32m➔[39m [32m| NodeJS Version: 8.11.4 - x64 |[39m [32m➔[39m [32m| MongoDB Version: 4.0.10 |[39m [32m➔[39m [32m| MongoDB Engine: wiredTiger |[39m [32m➔[39m [32m| Platform: linux |[39m [32m➔[39m [32m| Process Port: 3000 |[39m [32m➔[39m [32m| Site URL: http://10.0.0.4:3000 |[39m [32m➔[39m [32m| ReplicaSet OpLog: Enabled |[39m [32m➔[39m [32m| Commit Hash: 7475d7628a |[39m [32m➔[39m [32m| Commit Branch: HEAD |[39m [32m➔[39m [32m| |[39m [32m➔[39m [32m+---------------------------------------------+[39m
-
what is the error message in you are getting ?
-
I got it! Create folder mongodb in /mnt/user/appdata/ add mongod.conf in that folder: # mongod.conf # for documentation of all options, see: # http://docs.mongodb.org/manual/reference/configuration-options/ # Where and how to store data. storage: dbPath: /data/db journal: enabled: true # engine: # mmapv1: # wiredTiger: # network interfaces net: port: 27017 bindIp: 127.0.0.1 # how the process runs processManagement: timeZoneInfo: /usr/share/zoneinfo #security: #operationProfiling: replication: replSetName: "rs01" #sharding: ## Enterprise-Only Options: #auditLog: #snmp: Install MongoDB via communityapps. With added postargument "-f /data/db/mongod.conf" watch the log of mongodb if it start correctly. Install rocket.chat from communityapp Set Mono DB to your mongoDB, in my case it is "mongodb://10.0.0.4:27017/rocketchat" Set RocketChat URL to yor ip, in my case: "http://10.0.0.4:3000" Add another variable (plus icon) Start RocketChat watch the log and after a few minutes it should start up and you can connect.
-
Hello, a few weeks ago I had the same issue. After replacing it the sata cables the problem was gone for 3 days, and i posted solved before the next crash. So after more tinkering with different ram compinations, removing cache drive, replacing PSU/SATA Data cables and now a different Mainboard with differnt ram. I have the same issue again. Maybe it is the flash drive or something else ? docker ? If I remember correctly, the problem started to happen after the upgrade to 6.6.* from 6.5.* Current Configuration: MSI MS-7698/E350IS-E45 (an old itx board I had lying arround.) 2*2Gb DDR3 Ram 2*3TB HDD (Toshiba, Seagate) Bequiet PSU Unraid 6.7.0 Previous Configuration: Asrock j3455-itx 2 * 8Gb DDR3 So-Dimm 2*3TB HDD (Toshiba, Seagate) Enermax PSU Unraid 6.6.* All error messages did looked identical, but the process that is "not tainted" is different. Jun 14 12:55:48 nas kernel: BUG: Bad page map in process sleep pte:174a58025 pmd:802d1067 Jun 14 12:55:48 nas kernel: addr:00000000fa652a08 vm_flags:00000075 anon_vma: (null) mapping:00000000a9bdfd1e index:5c Jun 14 12:55:48 nas kernel: file:libc-2.29.so fault:shmem_fault mmap:shmem_mmap readpage: (null) Jun 14 12:55:48 nas kernel: CPU: 1 PID: 25867 Comm: sleep Not tainted 4.19.41-Unraid #1 Jun 14 12:55:48 nas kernel: Hardware name: MSI MS-7698/E350IS-E45 (MS-7698), BIOS V1.4 03/14/2011 Jun 14 12:55:48 nas kernel: Call Trace: Jun 14 12:55:48 nas kernel: dump_stack+0x5d/0x79 Jun 14 12:55:48 nas kernel: print_bad_pte+0x216/0x233 Jun 14 12:55:48 nas kernel: _vm_normal_page+0x50/0xb7 Jun 14 12:55:48 nas kernel: unmap_page_range+0x4b2/0x919 Jun 14 12:55:48 nas kernel: unmap_vmas+0x50/0x84 Jun 14 12:55:48 nas kernel: exit_mmap+0xb0/0x152 Jun 14 12:55:48 nas kernel: mmput+0x4d/0xe5 Jun 14 12:55:48 nas kernel: do_exit+0x3b0/0x919 Jun 14 12:55:48 nas kernel: do_group_exit+0x9a/0x9a Jun 14 12:55:48 nas kernel: __x64_sys_exit_group+0xf/0xf Jun 14 12:55:48 nas kernel: do_syscall_64+0x57/0xe6 Jun 14 12:55:48 nas kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 14 12:55:48 nas kernel: RIP: 0033:0x1549460797a6 Jun 14 12:55:48 nas kernel: Code: 00 4c 8b 0d ec 36 10 00 eb 19 66 2e 0f 1f 84 00 00 00 00 00 89 d7 89 f0 0f 05 48 3d 00 f0 ff ff 77 22 f4 89 d7 44 89 c0 0f 05 <48> 3d 00 f0 ff ff 76 e2 f7 d8 64 41 89 01 eb da 66 2e 0f 1f 84 00 Jun 14 12:55:48 nas kernel: RSP: 002b:00007ffd3d8c5fd8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 Jun 14 12:55:48 nas kernel: RAX: ffffffffffffffda RBX: 0000154946179760 RCX: 00001549460797a6 Jun 14 12:55:48 nas kernel: RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000 Jun 14 12:55:48 nas kernel: RBP: 0000000000000000 R08: 00000000000000e7 R09: ffffffffffffff80 Jun 14 12:55:48 nas kernel: R10: 00007ffd3d8c5ea4 R11: 0000000000000246 R12: 0000154946179760 Jun 14 12:55:48 nas kernel: R13: 0000000000000002 R14: 0000154946182428 R15: 0000000000000000 Jun 14 12:55:48 nas kernel: Disabling lock debugging due to kernel taint Jun 14 12:55:48 nas kernel: BUG: Bad rss-counter state mm:00000000b4343918 idx:3 val:1 Jun 14 12:56:01 nas kernel: BUG: Bad page map in process monitor pte:1742d1025 pmd:802d1067 Jun 14 12:56:01 nas kernel: addr:0000000020a7a50e vm_flags:00000075 anon_vma: (null) mapping:00000000ece0ddaa index:1c7 Jun 14 12:56:01 nas kernel: file:libcrypto.so.1.1 fault:shmem_fault mmap:shmem_mmap readpage: (null) Jun 14 12:56:01 nas kernel: CPU: 0 PID: 25932 Comm: monitor Tainted: G B 4.19.41-Unraid #1 Jun 14 12:56:01 nas kernel: Hardware name: MSI MS-7698/E350IS-E45 (MS-7698), BIOS V1.4 03/14/2011 Jun 14 12:56:01 nas kernel: Call Trace: Jun 14 12:56:01 nas kernel: dump_stack+0x5d/0x79 Jun 14 12:56:01 nas kernel: print_bad_pte+0x216/0x233 Jun 14 12:56:01 nas kernel: _vm_normal_page+0x50/0xb7 Jun 14 12:56:01 nas kernel: unmap_page_range+0x4b2/0x919 Jun 14 12:56:01 nas kernel: unmap_vmas+0x50/0x84 Jun 14 12:56:01 nas kernel: exit_mmap+0xb0/0x152 Jun 14 12:56:01 nas kernel: ? __switch_to_asm+0x35/0x70 Jun 14 12:56:01 nas kernel: mmput+0x4d/0xe5 Jun 14 12:56:01 nas kernel: do_exit+0x3b0/0x919 Jun 14 12:56:01 nas kernel: do_group_exit+0x9a/0x9a Jun 14 12:56:01 nas kernel: __x64_sys_exit_group+0xf/0xf Jun 14 12:56:01 nas kernel: do_syscall_64+0x57/0xe6 Jun 14 12:56:01 nas kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 14 12:56:01 nas kernel: RIP: 0033:0x154fb310c7a6 Jun 14 12:56:01 nas kernel: Code: Bad RIP value. Jun 14 12:56:01 nas kernel: RSP: 002b:00007ffeac426e08 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 Jun 14 12:56:01 nas kernel: RAX: ffffffffffffffda RBX: 0000154fb320c760 RCX: 0000154fb310c7a6 Jun 14 12:56:01 nas kernel: RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000 Jun 14 12:56:01 nas kernel: RBP: 0000000000000000 R08: 00000000000000e7 R09: ffffffffffffff78 Jun 14 12:56:01 nas kernel: R10: 0000000000000006 R11: 0000000000000246 R12: 0000154fb320c760 Jun 14 12:56:01 nas kernel: R13: 0000000000000007 R14: 0000154fb3215428 R15: 0000000000000000 Jun 14 12:56:01 nas kernel: BUG: Bad rss-counter state mm:0000000056072b79 idx:3 val:1 nas-diagnostics-20190614-1225.zip
-
[Solved] Unraid Docker service crashing and reboot not possible
mhlnstdt25 replied to mhlnstdt25's topic in General Support
Thanks for the tips, but that didn't help me to fix my problem. I replaced all S-ATA Data cables and that seems to fix the problems. -
[Solved] Unraid Docker service crashing and reboot not possible
mhlnstdt25 replied to mhlnstdt25's topic in General Support
Sorry missed that! nas-diagnostics-20190420-2224.zip -
Hello, my unraid instance does nearly daily report this (example) in the log and after that the docker service is acting weird (crashes some times) and a normal reboot is not possible. Only pulling the power plug is the option. Thinks I already tested: Update to 6.7Rc7 MemTest only using 1 Ram Module removed cache drive My Hardware: ASRock J3455-ITX 16GB Ram 2 * 3TB HDD (seagate + Toshiba) Docker Container running: Nextcloud + Maria DB Let's Encrypt (nginx) Pihole Hopefully anyone can help. Greetings Apr 20 09:30:01 nas kernel: BUG: unable to handle kernel paging request at ffff88866ff1cc00 Apr 20 09:30:01 nas kernel: PGD 2401067 P4D 2401067 PUD 0 Apr 20 09:30:01 nas kernel: Oops: 0000 [#1] SMP NOPTI Apr 20 09:30:01 nas kernel: CPU: 2 PID: 5219 Comm: php7 Not tainted 4.19.33-Unraid #1 Apr 20 09:30:01 nas kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./J3455-ITX, BIOS P1.80 05/21/2018 Apr 20 09:30:01 nas kernel: RIP: 0010:lock_hrtimer_base.isra.1+0x17/0x40 Apr 20 09:30:01 nas kernel: Code: 00 00 00 48 85 c0 74 08 48 89 c7 e8 56 e7 fc ff 31 c0 c3 41 54 49 89 f4 55 48 89 fd 53 48 8b 5d 00 48 81 fb 40 ef e3 81 74 1d <48> 8b 3b e8 c0 1b 5b 00 49 89 04 24 48 3b 5d 00 74 0f 48 8b 3b 48 Apr 20 09:30:01 nas kernel: RSP: 0018:ffffc90001dcbc00 EFLAGS: 00010287 Apr 20 09:30:01 nas kernel: RAX: 0000000000000000 RBX: ffff88866ff1cc00 RCX: 0000000000000006 Apr 20 09:30:01 nas kernel: RDX: 0000000000000000 RSI: ffffc90001dcbc30 RDI: ffff888404fac268 Apr 20 09:30:01 nas kernel: RBP: ffff888404fac268 R08: 00000000000005a8 R09: 000000000002cd80 Apr 20 09:30:01 nas kernel: R10: 00000000000163ec R11: 000000000002c7d8 R12: ffffc90001dcbc30 Apr 20 09:30:01 nas kernel: R13: 0000000000000000 R14: 000000000001cac0 R15: 0000000000000006 Apr 20 09:30:01 nas kernel: FS: 000014a6ff721b68(0000) GS:ffff88846ff00000(0000) knlGS:0000000000000000 Apr 20 09:30:01 nas kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 20 09:30:01 nas kernel: CR2: ffff88866ff1cc00 CR3: 00000003cf744000 CR4: 00000000003406e0 Apr 20 09:30:01 nas kernel: Call Trace: Apr 20 09:30:01 nas kernel: hrtimer_start_range_ns+0x57/0x1e2 Apr 20 09:30:01 nas kernel: ? get_nohz_timer_target+0x1b/0xe8 Apr 20 09:30:01 nas kernel: __tcp_transmit_skb+0x7de/0x912 Apr 20 09:30:01 nas kernel: tcp_write_xmit+0x979/0xd64 Apr 20 09:30:01 nas kernel: __tcp_push_pending_frames+0x2b/0x90 Apr 20 09:30:01 nas kernel: tcp_sendmsg_locked+0x9d7/0xb2e Apr 20 09:30:01 nas kernel: tcp_sendmsg+0x23/0x35 Apr 20 09:30:01 nas kernel: sock_sendmsg+0x14/0x1e Apr 20 09:30:01 nas kernel: __sys_sendto+0xcc/0x10a Apr 20 09:30:01 nas kernel: ? fuse_file_put+0x81/0x8e Apr 20 09:30:01 nas kernel: ? syscall_trace_enter+0x164/0x1a3 Apr 20 09:30:01 nas kernel: __x64_sys_sendto+0x1f/0x22 Apr 20 09:30:01 nas kernel: do_syscall_64+0x57/0xe6 Apr 20 09:30:01 nas kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Apr 20 09:30:01 nas kernel: RIP: 0033:0x14a6ff6e43ad Apr 20 09:30:01 nas kernel: Code: c3 8b 07 85 c0 75 24 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 <c3> e9 50 d7 ff ff 41 57 41 56 41 55 41 54 49 89 f4 55 53 48 89 fb Apr 20 09:30:01 nas kernel: RSP: 002b:00007fff21f32df8 EFLAGS: 00000246 ORIG_RAX: 000000000000002c Apr 20 09:30:01 nas kernel: RAX: ffffffffffffffda RBX: 000014a6ff721b68 RCX: 000014a6ff6e43ad Apr 20 09:30:01 nas kernel: RDX: 000000000000008f RSI: 000014a6ff2b6000 RDI: 0000000000000004 Apr 20 09:30:01 nas kernel: RBP: 000000000000002c R08: 0000000000000000 R09: 0000000000000000 Apr 20 09:30:01 nas kernel: R10: 0000000000000040 R11: 0000000000000246 R12: 000014a6ff2a6380 Apr 20 09:30:01 nas kernel: R13: 000000000000008f R14: 000014a6ff3d9828 R15: 000014a6ff2b6000 Apr 20 09:30:01 nas kernel: Modules linked in: veth macvlan xt_nat ipt_MASQUERADE iptable_nat nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod bonding x86_pkg_temp_thermal intel_powerclamp coretemp hid_logitech_hidpp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf r8169 i2c_i801 i2c_core hid_logitech_dj realtek ahci video libahci backlight thermal fan button pcc_cpufreq Apr 20 09:30:01 nas kernel: CR2: ffff88866ff1cc00 Apr 20 09:30:01 nas kernel: ---[ end trace f451f71b78ac40df ]--- Apr 20 09:30:01 nas kernel: RIP: 0010:lock_hrtimer_base.isra.1+0x17/0x40 Apr 20 09:30:01 nas kernel: Code: 00 00 00 48 85 c0 74 08 48 89 c7 e8 56 e7 fc ff 31 c0 c3 41 54 49 89 f4 55 48 89 fd 53 48 8b 5d 00 48 81 fb 40 ef e3 81 74 1d <48> 8b 3b e8 c0 1b 5b 00 49 89 04 24 48 3b 5d 00 74 0f 48 8b 3b 48 Apr 20 09:30:01 nas kernel: RSP: 0018:ffffc90001dcbc00 EFLAGS: 00010287 Apr 20 09:30:01 nas kernel: RAX: 0000000000000000 RBX: ffff88866ff1cc00 RCX: 0000000000000006 Apr 20 09:30:01 nas kernel: RDX: 0000000000000000 RSI: ffffc90001dcbc30 RDI: ffff888404fac268 Apr 20 09:30:01 nas kernel: RBP: ffff888404fac268 R08: 00000000000005a8 R09: 000000000002cd80 Apr 20 09:30:01 nas kernel: R10: 00000000000163ec R11: 000000000002c7d8 R12: ffffc90001dcbc30 Apr 20 09:30:01 nas kernel: R13: 0000000000000000 R14: 000000000001cac0 R15: 0000000000000006 Apr 20 09:30:01 nas kernel: FS: 000014a6ff721b68(0000) GS:ffff88846ff00000(0000) knlGS:0000000000000000 Apr 20 09:30:01 nas kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 20 09:30:01 nas kernel: CR2: ffff88866ff1cc00 CR3: 00000003cf744000 CR4: 00000000003406e0