![]() ![]() Fixed an issue where updating to DSM 7.2 might fail if users' Synology NAS weren't connected to the Internet.This update includes fixes to the below issues mentioned in 7.2-64561:.After installing this update, the current Windows Server 2008 domain and earlier versions will be unavailable. Starting from this version, only Windows Server 2008 R2 and above versions will be supported.The maximum single volume size supported by RS2423+/RS2423RP+ has been adjusted to 200 TB (with a minimum system memory requirement of 32 GB).However, to create a volume larger than 200 TB, a RAID 6 storage pool and at least 64 GB of system memory are still required. This update automatically converts existing volumes that use the Btrfs (Peta Volume) file system to Btrfs. Users can now create a Btrfs volume of up to 1 PB on specific Synology NAS models.Removed the "Automatically create port forwarding rules" option from QuickConnect advanced settings to increase network security.Starting from this version, logs for drives will no longer appear in Storage Manager > HDD and will be available only in Log Center.This update will restart your Synology NAS.After installing this update, you will not be able to downgrade to a previous DSM version.19:59:11,580 INFO Serviio DLNA media streaming server v 1.4.1-SNAPSHOT (rev. 11:59:50,179 DEBUG Validating license file (339 bytes) 10:59:51,058 DEBUG Validating license file (339 bytes) 09:59:50,398 DEBUG Validating license file (339 bytes) 08:59:51,874 DEBUG Validating license file (339 bytes) 07:59:56,032 INFO Added profile 'Generic DLNA profile' (id=1) 07:59:55,073 INFO Parsing Profiles definition 07:59:52,328 INFO Created UPnP Device with UUID: xxxxxxxx, bound address: x.x.x.x 07:59:51,544 DEBUG Validating license file (339 bytes) I added category and gave it DEBUG, while all the rest INFO, at 7:59. (First login, stopped Serviio and modifieded log4j.xml) Information,System,4 18:55:41,admin,User logged in from Information,System,4 19:16:17,SYSTEM,Internal disks woke up from hibernation. Information,System,4 21:05:14,SYSTEM,Internal disks woke up from hibernation. Information,System,4 22:08:57,SYSTEM,Internal disks woke up from hibernation. Information,System,4 22:24:06,SYSTEM,Internal disks woke up from hibernation. Information,System,4 22:24:25,admin,User logged in from Information,System,4 22:26:28,admin,User logged in from Information,System,4 23:27:23,SYSTEM,Internal disks woke up from hibernation. Information,System,5 00:27:23,SYSTEM,Internal disks woke up from hibernation. Information,System,5 01:27:23,SYSTEM,Internal disks woke up from hibernation. Information,System,5 02:27:24,SYSTEM,Internal disks woke up from hibernation. Information,System,5 03:27:23,SYSTEM,Internal disks woke up from hibernation. Information,System,5 04:27:23,SYSTEM,Internal disks woke up from hibernation. Information,System,5 05:27:24,SYSTEM,Internal disks woke up from hibernation. Information,System,5 06:27:24,SYSTEM,Internal disks woke up from hibernation. Information,System,5 06:47:40,SYSTEM,Internal disks woke up from hibernation. Information,System,5 06:47:49,admin,User logged in from As you can see there were regular wake ups at 1-hour interval. Today at 6:42 I logged in again and checked system log. All those network devices were still there but they might be less active. As there were network devices (PC, mobile etc) in the LAN of NAS I consider them normal.Īt 22:24 I logged in NAS and started Serviio. You can see in system log there were a few wake ups in irregular intervals. Then I let it be (Serviio stopped) for about 3.5 hours till 22:24. At 18:55 yesterday I stopped Serviio and changed in log4j.xml from DEBUG to ERROR. ![]()
0 Comments
Leave a Reply. |