bonienl Posted February 21, 2015 Share Posted February 21, 2015 Some additional notes: - Those using the dynamix band-aid plugin, should remove it BEFORE upgrading to B14. If removed AFTER the upgrade to B14 then a system reboot is required to unload the existing cron settings, which conflict with the new cron solution. - All notifications are OFF by default, and these need to be enabled on the notification settings page. Once enabled they will survive a system reboot - Settings for the scheduler (parity check) need to be re-applied to become active, this again is due to the new cron solution introduced in this version of unRAID - And ... clear your browser's cache to ensure the GUI is updated completely Quote Link to comment
johnodon Posted February 21, 2015 Share Posted February 21, 2015 Some additional notes: - Those using the dynamix band-aid plugin, should remove it BEFORE upgrading to B14. If removed AFTER the upgrade to B14 then a system reboot is required to unload the existing cron settings, which conflict with the new cron solution. - All notifications are OFF by default, and these need to be enabled on the notification settings page. Once enabled they will survive a system reboot - Settings for the scheduler (parity check) need to be re-applied to become active, this again is due to the new cron solution introduced in this version of unRAID - And ... clear your browser's cache to ensure the GUI is updated completely Most of this should be added to the OP. Quote Link to comment
johnodon Posted February 21, 2015 Share Posted February 21, 2015 Since we are telling everyone to recreate their docker image we really should provide a procedure how to do so in the least amount of steps whilst preserving container settings etc. +1 I'm afraid I'll do something stupid! Quote Link to comment
lars Posted February 21, 2015 Share Posted February 21, 2015 Since we are telling everyone to recreate their docker image we really should provide a procedure how to do so in the least amount of steps whilst preserving container settings etc. +1 sounds like the sensible thing to do! kinda good customer relation & pr-work , instead of telling ppl '...btw you will have to do this and that afterwards (and now go figure it out in the forum)...' many here poss. have little or none probs to deal with it, but many others looking at a potential scary and disastrous adventure cheers, L Quote Link to comment
HellDiverUK Posted February 21, 2015 Share Posted February 21, 2015 Approximately a minute or so after rebooting the server after applying the update there was a minor road traffic accident on the road that runs past my property. Is this an issue that limetech is aware of ? You must recreate your Docker image while sacrificing a chicken, making sure to upload a video of the minor traffic accident to YouTube. If no video is available, then you must sacrifice a goat while uninstalling apcupsd. After 613 reboots, of course. Quote Link to comment
sparklyballs Posted February 21, 2015 Share Posted February 21, 2015 Approximately a minute or so after rebooting the server after applying the update there was a minor road traffic accident on the road that runs past my property. Is this an issue that limetech is aware of ? You must recreate your Docker image while sacrificing a chicken, making sure to upload a video of the minor traffic accident to YouTube. If no video is available, then you must sacrifice a goat while uninstalling apcupsd. After 613 reboots, of course. I have a turkey thigh in the fridge and there is a small child available in lieu of the goat. Quote Link to comment
jonp Posted February 21, 2015 Share Posted February 21, 2015 Will update the OP later this morning (was up till 2am working with Tom to get this release tested / out). A hidden gem in beta 14 is the ability to delete your docker image from within the webGui. Quote Link to comment
BRiT Posted February 21, 2015 Share Posted February 21, 2015 A hidden gem in beta 14 is the ability to delete your docker image from within the webGui. You make it sound like randomly using the web ui will delete your docker.img. Quote Link to comment
jonp Posted February 21, 2015 Share Posted February 21, 2015 A hidden gem in beta 14 is the ability to delete your docker image from within the webGui. You make it sound like randomly using the web ui will delete your docker.img. Not what I meant I meant there is a check box on the docker page for deleting your existing image. It works similar to removing an empty share. Quote Link to comment
sparklyballs Posted February 21, 2015 Share Posted February 21, 2015 A hidden gem in beta 14 is the ability to delete your docker image from within the webGui. You make it sound like randomly using the web ui will delete your docker.img. right next to the "start auto self destruct sequence" button. Quote Link to comment
Darqfallen Posted February 21, 2015 Share Posted February 21, 2015 Just updated to beta 14 from beta 12. Noticed this in my syslog. Feb 21 07:27:22 Dirge kernel: ------------[ cut here ]------------ Feb 21 07:27:22 Dirge kernel: kernel BUG at fs/btrfs/inode.c:3123! Feb 21 07:27:22 Dirge kernel: invalid opcode: 0000 [#1] SMP Feb 21 07:27:22 Dirge kernel: Modules linked in: md_mod it87 hwmon_vid k10temp r8169 mii sata_sil i2c_piix4 ahci libahci Feb 21 07:27:22 Dirge kernel: CPU: 2 PID: 7466 Comm: btrfs-cleaner Not tainted 3.18.5-unRAID #3 Feb 21 07:27:22 Dirge kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./SABERTOOTH 990FX R2.0, BIOS 2103 11/06/2013 Feb 21 07:27:22 Dirge kernel: task: ffff8803f8064890 ti: ffff880007e14000 task.ti: ffff880007e14000 Feb 21 07:27:22 Dirge kernel: RIP: e030:[<ffffffff812cce1e>] [<ffffffff812cce1e>] btrfs_orphan_add+0xc8/0x15d Feb 21 07:27:22 Dirge kernel: RSP: e02b:ffff880007e17c58 EFLAGS: 00010286 Feb 21 07:27:22 Dirge kernel: RAX: 00000000ffffffe4 RBX: ffff8803f80a4800 RCX: 0000000000000000 Feb 21 07:27:22 Dirge kernel: RDX: 0000000001400140 RSI: 0000000016861684 RDI: ffff8803fb87a138 Feb 21 07:27:22 Dirge kernel: RBP: ffff880007e17c98 R08: 0000000000019cd0 R09: 0000000000000000 Feb 21 07:27:22 Dirge kernel: R10: 0000000000000000 R11: ffff880007e17c28 R12: ffff8803f89863f0 Feb 21 07:27:22 Dirge kernel: R13: ffff8803f8899160 R14: 0000000000000001 R15: 0000000000000001 Feb 21 07:27:22 Dirge kernel: FS: 00002adc4ef9cf40(0000) GS:ffff880418300000(0000) knlGS:0000000000000000 Feb 21 07:27:22 Dirge kernel: CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b Feb 21 07:27:22 Dirge kernel: CR2: 00002adc4fd6e488 CR3: 0000000001807000 CR4: 0000000000000660 Feb 21 07:27:22 Dirge kernel: Stack: Feb 21 07:27:22 Dirge kernel: ffff880007e17c98 ffff8803f80a4c58 0000000000000000 ffff8803f81b0e00 Feb 21 07:27:22 Dirge kernel: ffff8803f80a1800 ffff8803f889d630 ffff8803f89863f0 ffff8803f8899160 Feb 21 07:27:22 Dirge kernel: ffff880007e17d28 ffffffff812ba667 ffff8803f889d630 ffff8803f889d630 Feb 21 07:27:22 Dirge kernel: Call Trace: Feb 21 07:27:22 Dirge kernel: [<ffffffff812ba667>] btrfs_remove_block_group+0x11b/0x484 Feb 21 07:27:22 Dirge kernel: [<ffffffff812e8e33>] btrfs_remove_chunk+0x589/0x600 Feb 21 07:27:22 Dirge kernel: [<ffffffff812dec20>] ? free_extent_state.part.26+0x34/0x38 Feb 21 07:27:22 Dirge kernel: [<ffffffff812defe4>] ? free_extent_state+0x15/0x17 Feb 21 07:27:22 Dirge kernel: [<ffffffff812bab9b>] btrfs_delete_unused_bgs+0x1cb/0x207 Feb 21 07:27:22 Dirge kernel: [<ffffffff812c09a2>] cleaner_kthread+0x11b/0x14a Feb 21 07:27:22 Dirge kernel: [<ffffffff815fcb91>] ? _raw_spin_unlock_irqrestore+0x50/0x60 Feb 21 07:27:22 Dirge kernel: [<ffffffff812c0887>] ? btrfs_destroy_pinned_extent+0x9a/0x9a Feb 21 07:27:22 Dirge kernel: [<ffffffff81057486>] kthread+0xd6/0xde Feb 21 07:27:22 Dirge kernel: [<ffffffff810573b0>] ? kthread_create_on_node+0x172/0x172 Feb 21 07:27:22 Dirge kernel: [<ffffffff815fd0fc>] ret_from_fork+0x7c/0xb0 Feb 21 07:27:22 Dirge kernel: [<ffffffff810573b0>] ? kthread_create_on_node+0x172/0x172 Feb 21 07:27:22 Dirge kernel: Code: 01 72 08 41 be 01 00 00 00 eb 03 45 31 f6 48 8b 7d c8 e8 eb fc 32 00 45 85 f6 74 11 4c 89 e6 4c 89 ef e8 6c 7e fe ff 85 c0 74 02 <0f> 0b 41 ff cf 75 76 49 8b 94 24 68 fe ff ff 48 85 d2 74 0b 41 Feb 21 07:27:22 Dirge kernel: RIP [<ffffffff812cce1e>] btrfs_orphan_add+0xc8/0x15d Feb 21 07:27:22 Dirge kernel: RSP <ffff880007e17c58> Feb 21 07:27:22 Dirge kernel: ---[ end trace 6f663e95f806acc6 ]--- Just wondering what it is. Quote Link to comment
lars Posted February 21, 2015 Share Posted February 21, 2015 A hidden gem in beta 14 is the ability to delete your docker image from within the webGui. You make it sound like randomly using the web ui will delete your docker.img. ROFLMAO L Quote Link to comment
jonp Posted February 21, 2015 Share Posted February 21, 2015 Just updated to beta 14 from beta 12. Noticed this in my syslog. Feb 21 07:27:22 Dirge kernel: ------------[ cut here ]------------ Feb 21 07:27:22 Dirge kernel: kernel BUG at fs/btrfs/inode.c:3123! Feb 21 07:27:22 Dirge kernel: invalid opcode: 0000 [#1] SMP Feb 21 07:27:22 Dirge kernel: Modules linked in: md_mod it87 hwmon_vid k10temp r8169 mii sata_sil i2c_piix4 ahci libahci Feb 21 07:27:22 Dirge kernel: CPU: 2 PID: 7466 Comm: btrfs-cleaner Not tainted 3.18.5-unRAID #3 Feb 21 07:27:22 Dirge kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./SABERTOOTH 990FX R2.0, BIOS 2103 11/06/2013 Feb 21 07:27:22 Dirge kernel: task: ffff8803f8064890 ti: ffff880007e14000 task.ti: ffff880007e14000 Feb 21 07:27:22 Dirge kernel: RIP: e030:[<ffffffff812cce1e>] [<ffffffff812cce1e>] btrfs_orphan_add+0xc8/0x15d Feb 21 07:27:22 Dirge kernel: RSP: e02b:ffff880007e17c58 EFLAGS: 00010286 Feb 21 07:27:22 Dirge kernel: RAX: 00000000ffffffe4 RBX: ffff8803f80a4800 RCX: 0000000000000000 Feb 21 07:27:22 Dirge kernel: RDX: 0000000001400140 RSI: 0000000016861684 RDI: ffff8803fb87a138 Feb 21 07:27:22 Dirge kernel: RBP: ffff880007e17c98 R08: 0000000000019cd0 R09: 0000000000000000 Feb 21 07:27:22 Dirge kernel: R10: 0000000000000000 R11: ffff880007e17c28 R12: ffff8803f89863f0 Feb 21 07:27:22 Dirge kernel: R13: ffff8803f8899160 R14: 0000000000000001 R15: 0000000000000001 Feb 21 07:27:22 Dirge kernel: FS: 00002adc4ef9cf40(0000) GS:ffff880418300000(0000) knlGS:0000000000000000 Feb 21 07:27:22 Dirge kernel: CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b Feb 21 07:27:22 Dirge kernel: CR2: 00002adc4fd6e488 CR3: 0000000001807000 CR4: 0000000000000660 Feb 21 07:27:22 Dirge kernel: Stack: Feb 21 07:27:22 Dirge kernel: ffff880007e17c98 ffff8803f80a4c58 0000000000000000 ffff8803f81b0e00 Feb 21 07:27:22 Dirge kernel: ffff8803f80a1800 ffff8803f889d630 ffff8803f89863f0 ffff8803f8899160 Feb 21 07:27:22 Dirge kernel: ffff880007e17d28 ffffffff812ba667 ffff8803f889d630 ffff8803f889d630 Feb 21 07:27:22 Dirge kernel: Call Trace: Feb 21 07:27:22 Dirge kernel: [<ffffffff812ba667>] btrfs_remove_block_group+0x11b/0x484 Feb 21 07:27:22 Dirge kernel: [<ffffffff812e8e33>] btrfs_remove_chunk+0x589/0x600 Feb 21 07:27:22 Dirge kernel: [<ffffffff812dec20>] ? free_extent_state.part.26+0x34/0x38 Feb 21 07:27:22 Dirge kernel: [<ffffffff812defe4>] ? free_extent_state+0x15/0x17 Feb 21 07:27:22 Dirge kernel: [<ffffffff812bab9b>] btrfs_delete_unused_bgs+0x1cb/0x207 Feb 21 07:27:22 Dirge kernel: [<ffffffff812c09a2>] cleaner_kthread+0x11b/0x14a Feb 21 07:27:22 Dirge kernel: [<ffffffff815fcb91>] ? _raw_spin_unlock_irqrestore+0x50/0x60 Feb 21 07:27:22 Dirge kernel: [<ffffffff812c0887>] ? btrfs_destroy_pinned_extent+0x9a/0x9a Feb 21 07:27:22 Dirge kernel: [<ffffffff81057486>] kthread+0xd6/0xde Feb 21 07:27:22 Dirge kernel: [<ffffffff810573b0>] ? kthread_create_on_node+0x172/0x172 Feb 21 07:27:22 Dirge kernel: [<ffffffff815fd0fc>] ret_from_fork+0x7c/0xb0 Feb 21 07:27:22 Dirge kernel: [<ffffffff810573b0>] ? kthread_create_on_node+0x172/0x172 Feb 21 07:27:22 Dirge kernel: Code: 01 72 08 41 be 01 00 00 00 eb 03 45 31 f6 48 8b 7d c8 e8 eb fc 32 00 45 85 f6 74 11 4c 89 e6 4c 89 ef e8 6c 7e fe ff 85 c0 74 02 <0f> 0b 41 ff cf 75 76 49 8b 94 24 68 fe ff ff 48 85 d2 74 0b 41 Feb 21 07:27:22 Dirge kernel: RIP [<ffffffff812cce1e>] btrfs_orphan_add+0xc8/0x15d Feb 21 07:27:22 Dirge kernel: RSP <ffff880007e17c58> Feb 21 07:27:22 Dirge kernel: ---[ end trace 6f663e95f806acc6 ]--- Just wondering what it is. Looks like a btrfs bug. Why is it I can never recreate these in my test environments?!?! Quote Link to comment
Darqfallen Posted February 21, 2015 Share Posted February 21, 2015 Well right now the gui is recreating my docker img file. It is 50gigs and seems to be taking its time. If you require any more info let me know. Quote Link to comment
lars Posted February 21, 2015 Share Posted February 21, 2015 Just updated to beta 14 from beta 12. Noticed this in my syslog. Feb 21 07:27:22 Dirge kernel: ------------[ cut here ]------------ Feb 21 07:27:22 Dirge kernel: kernel BUG at fs/btrfs/inode.c:3123! Feb 21 07:27:22 Dirge kernel: invalid opcode: 0000 [#1] SMP Feb 21 07:27:22 Dirge kernel: Modules linked in: md_mod it87 hwmon_vid k10temp r8169 mii sata_sil i2c_piix4 ahci libahci Feb 21 07:27:22 Dirge kernel: CPU: 2 PID: 7466 Comm: btrfs-cleaner Not tainted 3.18.5-unRAID #3 Feb 21 07:27:22 Dirge kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./SABERTOOTH 990FX R2.0, BIOS 2103 11/06/2013 Feb 21 07:27:22 Dirge kernel: task: ffff8803f8064890 ti: ffff880007e14000 task.ti: ffff880007e14000 Feb 21 07:27:22 Dirge kernel: RIP: e030:[<ffffffff812cce1e>] [<ffffffff812cce1e>] btrfs_orphan_add+0xc8/0x15d Feb 21 07:27:22 Dirge kernel: RSP: e02b:ffff880007e17c58 EFLAGS: 00010286 Feb 21 07:27:22 Dirge kernel: RAX: 00000000ffffffe4 RBX: ffff8803f80a4800 RCX: 0000000000000000 Feb 21 07:27:22 Dirge kernel: RDX: 0000000001400140 RSI: 0000000016861684 RDI: ffff8803fb87a138 Feb 21 07:27:22 Dirge kernel: RBP: ffff880007e17c98 R08: 0000000000019cd0 R09: 0000000000000000 Feb 21 07:27:22 Dirge kernel: R10: 0000000000000000 R11: ffff880007e17c28 R12: ffff8803f89863f0 Feb 21 07:27:22 Dirge kernel: R13: ffff8803f8899160 R14: 0000000000000001 R15: 0000000000000001 Feb 21 07:27:22 Dirge kernel: FS: 00002adc4ef9cf40(0000) GS:ffff880418300000(0000) knlGS:0000000000000000 Feb 21 07:27:22 Dirge kernel: CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b Feb 21 07:27:22 Dirge kernel: CR2: 00002adc4fd6e488 CR3: 0000000001807000 CR4: 0000000000000660 Feb 21 07:27:22 Dirge kernel: Stack: Feb 21 07:27:22 Dirge kernel: ffff880007e17c98 ffff8803f80a4c58 0000000000000000 ffff8803f81b0e00 Feb 21 07:27:22 Dirge kernel: ffff8803f80a1800 ffff8803f889d630 ffff8803f89863f0 ffff8803f8899160 Feb 21 07:27:22 Dirge kernel: ffff880007e17d28 ffffffff812ba667 ffff8803f889d630 ffff8803f889d630 Feb 21 07:27:22 Dirge kernel: Call Trace: Feb 21 07:27:22 Dirge kernel: [<ffffffff812ba667>] btrfs_remove_block_group+0x11b/0x484 Feb 21 07:27:22 Dirge kernel: [<ffffffff812e8e33>] btrfs_remove_chunk+0x589/0x600 Feb 21 07:27:22 Dirge kernel: [<ffffffff812dec20>] ? free_extent_state.part.26+0x34/0x38 Feb 21 07:27:22 Dirge kernel: [<ffffffff812defe4>] ? free_extent_state+0x15/0x17 Feb 21 07:27:22 Dirge kernel: [<ffffffff812bab9b>] btrfs_delete_unused_bgs+0x1cb/0x207 Feb 21 07:27:22 Dirge kernel: [<ffffffff812c09a2>] cleaner_kthread+0x11b/0x14a Feb 21 07:27:22 Dirge kernel: [<ffffffff815fcb91>] ? _raw_spin_unlock_irqrestore+0x50/0x60 Feb 21 07:27:22 Dirge kernel: [<ffffffff812c0887>] ? btrfs_destroy_pinned_extent+0x9a/0x9a Feb 21 07:27:22 Dirge kernel: [<ffffffff81057486>] kthread+0xd6/0xde Feb 21 07:27:22 Dirge kernel: [<ffffffff810573b0>] ? kthread_create_on_node+0x172/0x172 Feb 21 07:27:22 Dirge kernel: [<ffffffff815fd0fc>] ret_from_fork+0x7c/0xb0 Feb 21 07:27:22 Dirge kernel: [<ffffffff810573b0>] ? kthread_create_on_node+0x172/0x172 Feb 21 07:27:22 Dirge kernel: Code: 01 72 08 41 be 01 00 00 00 eb 03 45 31 f6 48 8b 7d c8 e8 eb fc 32 00 45 85 f6 74 11 4c 89 e6 4c 89 ef e8 6c 7e fe ff 85 c0 74 02 <0f> 0b 41 ff cf 75 76 49 8b 94 24 68 fe ff ff 48 85 d2 74 0b 41 Feb 21 07:27:22 Dirge kernel: RIP [<ffffffff812cce1e>] btrfs_orphan_add+0xc8/0x15d Feb 21 07:27:22 Dirge kernel: RSP <ffff880007e17c58> Feb 21 07:27:22 Dirge kernel: ---[ end trace 6f663e95f806acc6 ]--- Just wondering what it is. you must have hit the the "start auto self destruct sequence" button sparklyballs just mentioned!!!! cheers, L Quote Link to comment
jonp Posted February 21, 2015 Share Posted February 21, 2015 Well right now the gui is recreating my docker img file. It is 50gigs and seems to be taking its time. If you require any more info let me know. Well so long as your system didn't crash, that's a good sign! Keep us posted. Quote Link to comment
TUMS Posted February 21, 2015 Share Posted February 21, 2015 Just to let the developers know, i'm still getting an empty dashboard. Hopefully you guys can fix it for the final release. Should be a known issue.. A few other people were having it also in the beta 12 thread. Quote Link to comment
HellDiverUK Posted February 21, 2015 Share Posted February 21, 2015 Just updated to b14 from b12, remotely via TeamViewer in to a VM on the unRAID box from my parent's house 80 miles away. It worked perfectly. How's that for living on the wild side? The "running Haswell at full speed" thing is still an issue. All 4 cores running at 3.6GHz constantly. i3-4350 on a B85 board (testing rig). Quote Link to comment
trurl Posted February 21, 2015 Share Posted February 21, 2015 Just to let the developers know, i'm still getting an empty dashboard. Hopefully you guys can fix it for the final release. Should be a known issue.. A few other people were having it also in the beta 12 thread. You cleared your browser cache and tried other browsers? Quote Link to comment
sparklyballs Posted February 21, 2015 Share Posted February 21, 2015 Just updated to b14 from b12, remotely via TeamViewer in to a VM on the unRAID box from my parent's house 80 miles away. It worked perfectly. How's that for living on the wild side? The "running Haswell at full speed" thing is still an issue. All 4 cores running at 3.6GHz constantly. i3-4350 on a B85 board (testing rig). my haswell (cpu in sig) was doing that, on b13 it was kernel panicking until i applied this fix. incidentally by reverting to the old cpu scaling, my haswell scales now. http://lime-technology.com/forum/index.php?topic=38193.msg354253#msg354253 Hopefully in a future release they'll nail the patch for haswell and negate the need for this "fix". Quote Link to comment
TUMS Posted February 21, 2015 Share Posted February 21, 2015 Just to let the developers know, i'm still getting an empty dashboard. Hopefully you guys can fix it for the final release. Should be a known issue.. A few other people were having it also in the beta 12 thread. You cleared your browser cache and tried other browsers? Sorry, yes I have. It's not just me that's having this issue. If you read back in the beta 12 thread quite a few people are having it. Quote Link to comment
Darqfallen Posted February 21, 2015 Share Posted February 21, 2015 Well right now the gui is recreating my docker img file. It is 50gigs and seems to be taking its time. If you require any more info let me know. Well so long as your system didn't crash, that's a good sign! Keep us posted. Well, it looks like the process is hung up as it shouldn't take this long to create a 50gb file on a ssd. root 8937 0.0 0.0 9336 2212 ? S 07:27 0:00 sh -c cd /usr/local/emhttp; /usr/bin/php /usr/local/src/wrap_post.php update.php '' '%23file=%2Fboot%2Fconfig%2Fdocker.cfg&%23command=%2Fetc%2Frc.d%2Frc.docker+start&DOCKER_ENABLED=yes&DOCKER_IMAGE_SIZE=50&DOCKER_IMAGE_FILE=%2Fmnt%2Fcache%2Fdocker%2Fdocker.img' root 8938 0.0 0.1 120684 16420 ? S 07:27 0:00 /usr/bin/php /usr/local/src/wrap_post.php update.php %23file=%2Fboot%2Fconfig%2Fdocker.cfg&%23command=%2Fetc%2Frc.d%2Frc.docker+start&DOCKER_ENABLED=yes&DOCKER_IMAGE_SIZE=50&DOCKER_IMAGE_FILE=%2Fmnt%2Fcache%2Fdocker%2Fdocker.img root 8939 0.0 0.0 9436 2476 ? S 07:27 0:00 /bin/sh /etc/rc.d/rc.docker start root 8943 0.0 0.0 8640 768 ? D 07:27 0:00 touch /mnt/cache/docker/docker.img Quote Link to comment
jonp Posted February 21, 2015 Share Posted February 21, 2015 Yes. Can you please post a defect report / syslog so we can investigate? Quote Link to comment
TUMS Posted February 21, 2015 Share Posted February 21, 2015 Yes. Can you please post a defect report / syslog so we can investigate? Sure, I'll try later today when I get home. I'm at work now. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.