/clr:implicitKeepAlive- is not documented

The command line help for cl.exe in VS2019 v16.10 mentions implicitKeepAlive- as an option, but it is not yet documented:
/clr[:option] compile for common language runtime, where option is:
    pure : produce IL-only output file (no native executable code)
    safe : produce IL-only verifiable output file
    netcore : produce assemblies targeting .NET Core runtime
    noAssembly : do not produce an assembly
    nostdlib : ignore the system .NET framework directory when searching for assemblies
    nostdimport : do not import any required assemblies implicitly
    initialAppDomain : enable initial AppDomain behavior of Visual C++ 2002
    implicitKeepAlive- : turn off implicit emission of System::GC::KeepAlive(this)

The documentation provided in the command line help is adequate for what the option does and could probably just be cloned here, but what's missing is "in what cases does the compiler automatically make calls to System::GC::KeepAlive(this)"?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a1d1e8ce-e0d5-321a-1cd3-8d96fecde8ad
Version Independent ID: 04343afb-ac3b-a7cb-6322-f5608442f554
Content: /clr (Common Language Runtime compilation)
Content Source: docs/build/reference/clr-common-language-runtime-compilation.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @corob-msft
Microsoft Alias: corob

@corob-msft: Can you elaborate the "other" race condition upon method return?
Will this issue manifest mainly as early GCed parent objects whose members dtors are called too early leading to NullReferenceExceptions or are also Managed Heap Corruptions expected?

@Alois-xx
My description of return handling may have been too broad. The compiler's placement of the KeepAlive call isn't magic relative to what's possible in source code. However, it may insert it later relative to what's found in the actual source code passed to the compiler. This is what the developer wrote about placement of the KeepAlive call relative to the return statement:

If we emit a System::GC::KeepAlive(this) call immediately preceding the return it still leaves
opportunity for the JIT compiler to deallocate this before the call to copyData() is complete.
E.g.,

auto Bridge::CallLong()
{
    return this->mPtr->copyData();
}

Fixing this edge case requires rewriting the return expression and inserting the KeepAlive call
at the appropriate place but doing this at the tree level proved impossible due to the penchant
for tree pattern matching in the compiler. This is instead done at IL Lower level.
So in code that looks like this example, a naive approach that just inserts a KeepAlive call before the return isn't sufficient to avoid the race. You may need to refactor your code slightly to prevent a possible GC during processing of your return statement. That's essentially what the compiler does here.

As for how the premature GC issue manifests, I'd expect null reference exceptions. I don't know enough to say you can't get managed heap corruption, but that's not the usual result of running finalizers.

@corob-msft : Thanks for the clarification.
The race condition comes from finalizers but if Bridge does not contain a finalizer GC.KeepAlive is also emitted as you noted by the rules above. This means that if a managed class has a member variable which holds some finalizable object then you also have a race condition which is prevented by this fix.
It all boils down to executing finalizers for objects which unmanaged method call still might be needing.
This would then show up at runtime as invalid handles, nulled out memory, already released memory, closed sockets, files, ...  and such things.

Thank you for your patience as we work through our backlog. We have received more issues than we can manage at this time. We are closing issues based on their severity, how broadly applicable they are, and whether there is enough information provided to act on the issue. If you believe that this issue should not have been closed, please add a comment explaining why by 3/1/2024. We appreciate your contribution and encourage you to propose changes using public PRs, or submit feedback through our updated control at the top of the page, as we phase out Git Issues for this repo. For more information on our feedback systems, see https://aka.ms/ContentUserFeedback.


Don't remove group with only remote files

Created the test first and confirmed it failed. I've not yet had time to see if there are any similar bugs in other areas of the dependencies code - only taken a look at the removal case so far.
Edit: I've also added an extra fix for building on a path with spaces, though this still fails after due to a similar bug in the dotnet core targets file which I've reported here: https://github.com/dotnet/netcorecli-fsc/issues/59

cool thx!


Fix a NoThunks test failure on nightly builds

Description
There's a strictness bug in Data.Map.Strict.fromDistinctAscList and this PR adds a workaround for it.
I've also also submitted a PR to containers.
Closes #4184
Checklist

[x] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[ ] The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[ ] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[x] Self-reviewed the diff

I made sure to put the word "nightly" in the title, so the PR CI is running the nightly tests. Glad we chose to add that feature to the workflow!

Related: https://github.com/nick8325/quickcheck/pull/384
We can revert this change when that is merged in QuickCheck and we bump the version here.

We can revert this change when that is merged in QuickCheck and we bump the version here.

Actually, this change works around a bug in containers, not QuickCheck. The QuickCheck PR fixes a real problem that I discovered during investigation of #4184, but it turned out not to be the one that was causing our test failures.

The containers PR is here

I also discovered why the test failures were happening only with ghc 9.8, and that's because the containers bug was introduced with a recent version of containers (0.6.8) and the boot packages of earlier ghc's contain older versions.

Sadly, it will take a bit of manual retrying to get the CI to pass again, because of the other flaky tests that fail in nightly. It's random as to which of the four ghc versions those will fail in, and each job takes about 4h.


Add unions

Currently there is no way to specify union types, which ends up being a problem for structs such as std::result[[T, E]] which can only ever hold a T or an E, but presently require sizeof(T) + sizeof(E) + tag_bool + padding space. Sunder is an imperative language at its core, so I don't think I want to venture into the realm of tagged-unions/variants just yet, but it would be nice to have something at least at the level of C's union types.
One solution could be to have union be wrapper around certain members of a struct rather than its own distinct thing. So std::result[[T, E]] would be implemented as:
struct result[[T, E]] {
    union {
        var _value: T;
        var _error: E;
    }
    var _is_value: bool;
}

I took a stab at this, and ran into a couple of issues, the main one being that struct initializers will produce an error if all elements are not assigned a value. There needs to be a way to say "one member of the union has been initialized". I originally tried adding everything in the union as member variables with the same starting max-aligned-of-the-types-offset, but without encoding this extra information initializers just didn't work. If you ignore the code that checks for all member variables are assigned, then you will get failures when evaluating constant expressions as some variable elements are NULL when passed to eval_rvalue.
Both of these issues can be worked around, but it feels kinda hacky, and I don't want to add more hacks the the compiler right now. The language behaves just fine without unions, and honestly a slightly larger than necessary std::result isn't the end of the world, so for now I'm going to shelve the implementation of unions and circle back to this issue once the compiler has been cleaned up a bit more.

Despite not intending to add unions to the language. Commit 5112f032a09e27143a8758f7b5334b843d2adc24 actually contains the MVP for union declarations and expressions, using syntax similar to structs.


Ruby 3.1: Parse forward arg without parentheses

Part of Ruby 3.1 support
https://github.com/whitequark/parser/commit/bb6c4a8e22917fafa1ba9e1b99a3b6598791a694
https://bugs.ruby-lang.org/issues/18267
Motivation

Allowing developers to use Sorbet with Ruby 3.1
Test plan

See included automated tests.
cc @Morriar

but I'd like @jez to take a look as well.

Heads up I'm unlikely to have time to review this until next week sometime, but I'll be sure to make a note to look then.


Update cloud_run_v2 worker logo url

Thank you for your willingness to contribute to prefect-gcp! The code for this library has been moved to https://github.com/PrefectHQ/prefect/tree/main/src/integrations/prefect-gcp. Please reopen this PR there if this functionality is still needed!


Update the Logic for retrieving Package Properties

Updates to Get-javascript-PackageInfoFromRepo
Depends on https://github.com/Azure/azure-sdk-tools/pull/1418

Seems like this PR is mixed up with some other changes.

That seems to have been an issue with Github. It cleared up by itself without me doing anything.


ElasticTransformation incorrect filling new pixels

For all other geometric augmentations, when applied to 3-channel pictures cval value interpreted as (cval,cval,cval), so you can set either black/gray/white filling of emerged pixels. However, for Elastic Transformation setting cval=255 leads to red pixels. That is happening because cv2.remap takes RGB tuple for 3-channel images for borderValue. If integer passed, it is used as (cval,0,0), hence producing red pixels.
I'm not sure this is correct way to fix this issue, but at least on my setup it works.

Codecov Report

Merging #561 into master will decrease coverage by 0.5%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #561     +/-   ##
=========================================
- Coverage   96.43%   95.94%   -0.5%
=========================================
  Files          38       38
  Lines       13933    13933
=========================================
- Hits        13436    13367     -69
- Misses        497      566     +69

Nice, thanks a lot for pointing this one out. There were tests for the cval in ElasticTransformation, but they all operated with (H, W) images instead of (H, W, 3), so this wasn't caught.
The way it is implemented should be good for now. The cval should probably be sampled channelwise at some point so that e.g. RGB values and not just intensity values are possible. But that can be reserved for a follow-up patch.

Merged.


Project alive?

Is this project still alive? Or has it been superceded by another Haskell Ethereum implementation?

See https://github.com/blockapps

Thanks! I'm not sure how that answers the question though...?

...and will it support Homestead? its out for some time and other clients all have a compatible impl. is there a reason ethereumH doesnt?

We've had a homestead compatible implementation for some time, we just haven't fully announced it.

Ok, thanks! Would be good to update at least this: http://www.ethdocs.org/en/latest/ethereum-clients/choosing-a-client.html because ethereumH is the last one on this page not supporting Homestead.

http://ethereum.stackexchange.com/q/5818/87

See https://github.com/blockapps

This? https://github.com/blockapps/ethereumH


Web: cross browser testing

Refs: none

[ ] macOS @mjbvz
[ ] Linux @octref
[ ] Windows @sbatten
[ ] iPadOS @rebornix

Complexity: 4

Make sure you have latest browsers installed:

macOS: Safari, Firefox
Linux: Firefox
Windows: Firefox

Do exploratory testing in the assigned browsers (macOS: both Safari and Firefox) and report issues here (use the browser specific labels to signal the browser).
Also watch out for rendering issues and messages printed to the developer console that could hint to issues.
Areas:

Editor usage
Layout / Grid / View Manipulation
File manipulation
Search
Debugging (e.g. debug hello world extension)
Terminal
Problems
SCM, Diff
Extensions Management
Settings
etc...

@rebornix fyi I added you for iPadOS testing (if possible) with keyboard and mouse. Feel free to pass along a test plan item in return to me 👍

@bpasero Not sure if I should assign to you or the area owners, I assigned you for now so it show up in your notification, feel free to give to others.

That is ok, thanks.

Also I didn't open an issue, but Ctrl+Shift+P is bound by Firefox and not being able to override that is not feeling good.

Finished my first round of iPadOS/iOS testing, in overall it works as expected. Some core components feel wrong for following reasons

We didn't listen to Pointer Events https://github.com/microsoft/vscode/issues/83719
We didn't handle touch down/drag/move properly https://github.com/microsoft/vscode/issues/83720
iOS particular safe area / visual area management

Rest of the issues are mostly minor ux issues from my limited testing. IMO after we have above three major painpoints resolved then we can do more testing on iOS/iPadOS/touchscreen to see how we can provide smooth experience.


Easy access to defined schema and schema sample

Suppose we have the following code:
class MySerializer
  include Surrealist
  json_schema do
    { name: String, age: Int }
  end
end

get '/foo' do
  # returns json using MySerializer
  present AnyClass.get_data(params), with: MySerializer
end

In my request test I want to test the api without overtesting AnyClass, so I mock the return of get_data:
it do
  expect(AnyClass).to receive(:get_data).and_return(data)
  get '/foo'
end

the data variable has to match the schema defined in MySerializer, so, I created a piece of code that generates a hash (because I am using my hack to accept hash) based on my defined schema (set with json_schema) to be DRY (so I dont have to mock manually).
I had to do instance_variable_get('@__surrealist_schema') to get the defined schema..
What if we could do just MySerializer.defined_schema to get the defined schema?
Going further..
What if we could do just MySerializer.schema_sample to get a sample of the schema, something like:
{ name: "", age: 0 }

Then I could do this in my test instead of having to define by myself a schema matching hash for the mock:
let(:data) { MySerializer.schema_sample }

Full demo: https://gist.github.com/glaucocustodio/85217a4e153407f053ae0cb60144a189

Hey @glaucocustodio, thank you for this proposal. I have been thinking myself about some kind of a schema-testing instrument, but I had some kind of a rspec/minitest matcher in mind, like
expect(JSON.parse(response)).to match_schema_of(MySerializer)

But I guess a method will also do for some cases, so I would be glad accepting a PR with it's implementation. And Rspec/MiniTest matcher would be just awesome.
Concerning schema samples, I think there's a lot of things to consider here, because there are more types than just Integer, String or Bool. I think we should create a separate issue to discuss this proposal, what do you think?

We need to think about this matcher because JSON.parse(response) convert hash keys to string and the schema very likely will be as symbol.
Should we use deep_stringify_keys or deep_symbolize_keys from ActiveSupport ou should we implement by ourselves?

Hi @nulldef, I don't want to test the schema with requests spec.
I want to test only the endpoint, so I mock the implementation class behind it, but the serializer in use, expects to receive a valid json schema. To avoid my request spec to know about the schema, would be nice if I could generate a sample schema using MySerializer.schema_sample by example.

@glaucocustodio
if we add a method like schema_sample - request spec will be known about the schema.

I want to test only the endpoint

What does it mean? That endpoint returns 200OK?

I dont see how the endpoint will not be bounded to the response schema.
Either I use something to "automate" my work or I have to mock one manually (because the serializer validates the given schema).

What does it mean?
Status code, content-type, response body matching the class return being called.

I'm sure that expect(response.body).to eq(MySerializer.defined_schema) is enough

To get a response.body matching the defined_schema I have to mock one to pass to MySerializer.
I want to ease this mocking, by not having to write one by myself, instead, getting one with schema_sample.

Sorry, but I can't understand why you have to mock defined_schema method.

Hey, @glaucocustodio are you planning to do something with this issue? Or is something blocking it?

I have given it a thought and I guess no, it does not make sense to add this to the surrealist gem itself. Maybe later we can implement some kind of surrealist-rspec with schema_sample and expect(...).to match_schema_of(Serializer).
I will close this for now, feel free to reopen it if you have any questions.


Implementing CNN for Text Classification in MXNet

It is slightly simplified implementation of Kim's Convolutional Neural Networks for Sentence Classification paper in MXNet.
Recently, I have been learning mxnet for Natural Language Processing (NLP). I followed this nice blog "Implementing a CNN for Text Classification in Tensorflow"  to reimplement it by mxnet framwork.

Could you change the folder name cnn to something more informative?
like cnn_text_classification?
Otherwise LGTM

ok, I will update it, thanks

Thanks! This is merged


360 Related Issues - Plots

Report related issues:
http://hades:62495/files/hades/Rona/360v110/QC2/BareBonesReport.html#quality-control-details

[x] HK QC plots display RCC file names instead of sample names

[x] LOD QC plots

LOD plot boxplots still display only one boxplot for all samples.

LOD plot boxplots still display only one boxplot for all samples.

@rvitancol can you point me to your config. I think I need to step through to find the issue.

@rvitancol can you point me to your config. I think I need to step through to find the issue.

@NicoleEO
\hades\share\Rona\360v110\QC2\BareBonesReport

@NicoleEO
\hades\share\Rona\360v110\QC2\BareBonesReport

@rvitancol the LOD plot is fixed now.

@rvitancol the LOD plot is fixed now.


Run locally on a PC?

Hi!
I'm searching for a tool to bring MathType equations into inkscape. This tool looks promising, but I don't accept cloud. Is it possible to run this locally?

You can download and build it yourself, and then serve the build directory locally and run it in your browser.
$ yarn install

$ yarn build

$ npm install -g serve
$ serve dist/

OK, please excuse my total utter noobness at internet technologies.
I'm on Win10.
So I need to install Yarn package manager. Then install Node.js to have npm. Then download zip of the repo. Then open command prompt/terminal there, and run the commands you provided. Now, what should I open in the browser?


Packaging and deployment tool for XAF winform APP

Hi,
I would like to deploy a winform app but i had really bad experience with ClickOnce.
After looking a bit I discovered Squirrel which is very simple but apparently the project is not being maintained anymore.
Do you have a suggestion on what i could use for the winform to package and manage the updates for the XAF app ? Windows bridge is not a option as i have customers with Windows 7.
You expertise would be welcome :-)
BR
ISA

Moreover i cannot use the Xaf updater as i do not user moduleinfo :-(

I do not have deployment exeperience, however I know that XAF users use clickonce with success. The clickonce technology however takes too much initiatives and hides stuff in order to automate the deployment. It really depends on your scenario, however a zip with all assemblies it should work the same

Thanks Tolis.
Just for info there are some interesting suggestions from Dennis in this ticket :
https://www.devexpress.com/Support/Center/Question/Details/T806232/packaging-and-deployment-tool-for-xaf-winform-app


[Bug]: unhealthy since update to dsm 7.2.2-72806 Update 2

Operating system
debian bookworm
Description
the issue from #465 reappeared the difference to my issue is, there is no firewall activated in DSM.
DSM boots fine, no issues with docker logs or dmesg or such.
The health script messages are the same as of #465 but dsm is reachable at <IP_ADDRESS>:5000 (macvlan) fine.
Nothing changed within config. Only upgraded to latest DSM
Docker compose
services:
synology:
container_name: o365backup
image: vdsm/virtual-dsm
environment:
  DISK_SIZE: "16G"
  DISK2_SIZE: "10.5TB"
  RAM_SIZE: "8G"
  CPU_CORES: "4"
  MAC: "02-11-32-21-27-9B"
  URL: "https://global.synologydownload.com/download/DSM/release/7.2.2/72806/DSM_VirtualDSM_72806.pat"
devices:
  - /dev/vhost-net
  - /dev/kvm
cap_add:
  - NET_ADMIN
ports:
  - 5000:5000
volumes:
  - /srv/dev-disk-by-uuid-b373f1da-6e2f-4cae-bd26-b795e52faadb/backup2/synology/config:/storage
  - /srv/dev-disk-by-uuid-b373f1da-6e2f-4cae-bd26-b795e52faadb/backup2:/storage2
stop_grace_period: 2m
networks:
  vdsm_eno1:
    ipv4_address: <IP_ADDRESS>
dns:
  - "<IP_ADDRESS>"

networks:
vdsm_eno1:
external: true
Docker log
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.302+ (root@build6) (gcc version 12.2.0 (GCC) ) #72806 SMP Thu Sep 5 13:41:22 CST 2024
[    0.000000] Command line: root=/dev/sda1 ihd_num=0 netif_num=0 syno_hw_version=VirtualDSM vender_format_version=2 macs=00211d050564,00211d050565,00211d050566,00211d050567
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007ffd3fff] usable
[    0.000000] BIOS-e820: [mem 0x000000007ffd4000-0x000000007fffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000027fffffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] extended physical RAM map:
[    0.000000] reserve setup_data: [mem 0x0000000000000000-0x000000000009fbff] usable
[    0.000000] reserve setup_data: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[    0.000000] reserve setup_data: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[    0.000000] reserve setup_data: [mem 0x0000000000100000-0x0000000001df2967] usable
[    0.000000] reserve setup_data: [mem 0x0000000001df2968-0x0000000001df2977] usable
[    0.000000] reserve setup_data: [mem 0x0000000001df2978-0x000000007ffd3fff] usable
[    0.000000] reserve setup_data: [mem 0x000000007ffd4000-0x000000007fffffff] reserved
[    0.000000] reserve setup_data: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
[    0.000000] reserve setup_data: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[    0.000000] reserve setup_data: [mem 0x00000000feffc000-0x00000000feffffff] reserved
[    0.000000] reserve setup_data: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
[    0.000000] reserve setup_data: [mem 0x0000000100000000-0x000000027fffffff] usable
[    0.000000] SMBIOS 2.8 present.
[    0.000000] Hypervisor detected: KVM
[    0.000000] Kernel/User page tables isolation: disabled
[    0.000000] e820: last_pfn = 0x280000 max_arch_pfn = 0x400000000
[    0.000000] x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WB  WT  UC- UC
[    0.000000] e820: last_pfn = 0x7ffd4 max_arch_pfn = 0x400000000
[    0.000000] found SMP MP-table at [mem 0x000f5440-0x000f544f] mapped at [ffff8800000f5440]
[    0.000000] Using GB pages for direct mapping
[    0.000000] RAMDISK: [mem 0x7fa55000-0x7ffc3fff]
[    0.000000] ACPI: Early table checksum verification disabled
[    0.000000] ACPI: RSDP 0x00000000000F5260 000014 (v00 BOCHS )
[    0.000000] ACPI: RSDT 0x000000007FFE2364 000034 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
[    0.000000] ACPI: FACP 0x000000007FFE217C 0000F4 (v03 BOCHS  BXPC     00000001 BXPC 00000001)
[    0.000000] ACPI: DSDT 0x000000007FFE0040 00213C (v01 BOCHS  BXPC     00000001 BXPC 00000001)
[    0.000000] ACPI: FACS 0x000000007FFE0000 000040
[    0.000000] ACPI: APIC 0x000000007FFE2270 000090 (v03 BOCHS  BXPC     00000001 BXPC 00000001)
[    0.000000] ACPI: MCFG 0x000000007FFE2300 00003C (v01 BOCHS  BXPC     00000001 BXPC 00000001)
[    0.000000] ACPI: WAET 0x000000007FFE233C 000028 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
[    0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
[    0.000000] kvm-clock: cpu 0, msr 2:7fffc001, primary cpu clock
[    0.000000] kvm-clock: using sched offset of<PHONE_NUMBER>637 cycles
[    0.000000] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns:<PHONE_NUMBER>83 ns
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.000000]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.000000]   Normal   [mem 0x0000000100000000-0x000000027fffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000001000-0x000000000009efff]
[    0.000000]   node   0: [mem 0x0000000000100000-0x000000007ffd3fff]
[    0.000000]   node   0: [mem 0x0000000100000000-0x000000027fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000027fffffff]
[    0.000000] ACPI: PM-Timer IO Port: 0x608
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[    0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
[    0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
[    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000effff]
[    0.000000] PM: Registered nosave memory: [mem 0x000f0000-0x000fffff]
[    0.000000] PM: Registered nosave memory: [mem 0x01df2000-0x01df2fff]
[    0.000000] PM: Registered nosave memory: [mem 0x01df2000-0x01df2fff]
[    0.000000] PM: Registered nosave memory: [mem 0x7ffd4000-0x7fffffff]
[    0.000000] PM: Registered nosave memory: [mem 0x80000000-0xafffffff]
[    0.000000] PM: Registered nosave memory: [mem 0xb0000000-0xbfffffff]
[    0.000000] PM: Registered nosave memory: [mem 0xc0000000-0xfed1bfff]
[    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
[    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffbfff]
[    0.000000] PM: Registered nosave memory: [mem 0xfeffc000-0xfeffffff]
[    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xfffbffff]
[    0.000000] PM: Registered nosave memory: [mem 0xfffc0000-0xffffffff]
[    0.000000] e820: [mem 0xc0000000-0xfed1bfff] available for PCI devices
[    0.000000] Booting paravirtualized kernel on KVM
[    0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>391419 ns
[    0.000000] setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:4 nr_node_ids:1
[    0.000000] PERCPU: Embedded 37 pages/cpu @ffff88027fc00000 s111896 r8192 d31464 u524288
[    0.000000] KVM setup async PF for cpu 0
[    0.000000] kvm-stealtime: cpu 0, msr 27fc14180
[    0.000000] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes)
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 2064220
[    0.000000] Kernel command line: root=/dev/sda1 ihd_num=0 netif_num=0 syno_hw_version=VirtualDSM vender_format_version=2 macs=00211d050564,00211d050565,00211d050566,00211d050567
[    0.000000] Internal HD num: 0
[    0.000000] Internal netif num: 0
[    0.000000] Synology Hardware Version: VirtualDSM
[    0.000000] Vender format version: 2
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[    0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
[    0.000000] Memory: 8160520K/8388040K available (5435K kernel code, 870K rwdata, 1712K rodata, 1008K init, 1556K bss, 227520K reserved, 0K cma-reserved)
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 64.
[    0.000000]  RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=4.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
[    0.000000] NR_IRQS:8448 nr_irqs:456 16
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [ttyS0] enabled
[    0.000000] tsc: Detected 2197.454 MHz processor
[    0.269479] Calibrating delay loop (skipped) preset value.. 4394.90 BogoMIPS (lpj=2197454)
[    0.271068] pid_max: default: 32768 minimum: 301
[    0.272073] ACPI: Core revision 20150930
[    0.273604] ACPI: 1 ACPI AML tables successfully acquired and loaded
[    0.274894] Security Framework initialized
[    0.275717] AppArmor: AppArmor initialized
[    0.276515] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
[    0.277732] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
[    0.279444] Initializing cgroup subsys io
[    0.280179] Initializing cgroup subsys memory
[    0.280992] Initializing cgroup subsys devices
[    0.281775] Initializing cgroup subsys freezer
[    0.282619] CPU: Physical Processor ID: 0
[    0.283323] CPU: Processor Core ID: 0
[    0.284792] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[    0.285789] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
[    0.286944] Speculative Store Bypass: Vulnerable
[    0.289747] Freeing SMP alternatives memory: 24K
[    0.297343] x2apic enabled
[    0.298197] Switched APIC routing to physical x2apic.
[    0.300400] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.301614] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz (family: 0x6, model: 0x4f, stepping: 0x1)
[    0.303464] Performance Events: 16-deep LBR, Broadwell events, full-width counters, Intel PMU driver.
[    0.329068] ... version:                2
[    0.330624] ... bit width:              48
[    0.332219] ... generic registers:      4
[    0.334143] ... value mask:             0000ffffffffffff
[    0.336682] ... max period:             00007fffffffffff
[    0.339169] ... fixed-purpose events:   3
[    0.341100] ... event mask:<PHONE_NUMBER>00000f
[    0.343511] KVM setup paravirtual spinlock
[    0.345926] x86: Booting SMP configuration:
[    0.347767] .... node  #0, CPUs:      #1
[    0.350014] kvm-clock: cpu 1, msr 2:7fffc041, secondary cpu clock
[    0.355877] KVM setup async PF for cpu 1
[    0.356465]  #2
[    0.356465] kvm-clock: cpu 2, msr 2:7fffc081, secondary cpu clock
[    0.359788] KVM setup async PF for cpu 2
[    0.359798] kvm-stealtime: cpu 2, msr 27fd14180
[    0.360224]  #3
[    0.360224] kvm-clock: cpu 3, msr 2:7fffc0c1, secondary cpu clock
[    0.363693] x86: Booted up 1 node, 4 CPUs
[    0.363697] smpboot: Total of 4 processors activated (17579.63 BogoMIPS)
[    0.363698] KVM setup async PF for cpu 3
[    0.363708] kvm-stealtime: cpu 3, msr 27fd94180
[    0.373226] kvm-stealtime: cpu 1, msr 27fc94180
[    0.375560] devtmpfs: initialized
[    0.377108] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>275000 ns
[    0.380009] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.382883] NET: Registered protocol family 16
[    0.389460] cpuidle: using governor ladder
[    0.395896] cpuidle: using governor menu
[    0.397148] ACPI: bus type PCI registered
[    0.398341] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.400573] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xb0000000-0xbfffffff] (base 0xb0000000)
[    0.403252] PCI: MMCONFIG at [mem 0xb0000000-0xbfffffff] reserved in E820
[    0.405250] PCI: Using configuration type 1 for base access
[    0.412986] ACPI: Added _OSI(Module Device)
[    0.414190] ACPI: Added _OSI(Processor Device)
[    0.415439] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.416745] ACPI: Added _OSI(Processor Aggregator Device)
[    0.421755] ACPI: Interpreter enabled
[    0.422817] ACPI: (supports S0 S4 S5)
[    0.423872] ACPI: Using IOAPIC for interrupt routing
[    0.425301] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.430738] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    0.432483] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[    0.434714] acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug]
[    0.436611] acpi PNP0A08:00: _OSC: OS now controls [PME AER PCIeCapability]
[    0.438761] PCI host bridge to bus 0000:00
[    0.439898] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
[    0.441498] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
[    0.443115] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[    0.444875] pci_bus 0000:00: root bus resource [mem 0x80000000-0xafffffff window]
[    0.446629] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window]
[    0.448399] pci_bus 0000:00: root bus resource [mem 0x380000000000-0x3807ffffffff window]
[    0.450315] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.530935] pci 0000:00:1f.0: quirk: [io  0x0600-0x067f] claimed by ICH6 ACPI/GPIO/TCO
[    0.542744] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
[    0.544125] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
[    0.545399] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
[    0.546739] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
[    0.548023] ACPI: PCI Interrupt Link [LNKE] (IRQs 5 *10 11)
[    0.549219] ACPI: PCI Interrupt Link [LNKF] (IRQs 5 *10 11)
[    0.550407] ACPI: PCI Interrupt Link [LNKG] (IRQs 5 10 *11)
[    0.551818] ACPI: PCI Interrupt Link [LNKH] (IRQs 5 10 *11)
[    0.552935] ACPI: PCI Interrupt Link [GSIA] (IRQs *16)
[    0.553914] ACPI: PCI Interrupt Link [GSIB] (IRQs *17)
[    0.554899] ACPI: PCI Interrupt Link [GSIC] (IRQs *18)
[    0.555970] ACPI: PCI Interrupt Link [GSID] (IRQs *19)
[    0.556956] ACPI: PCI Interrupt Link [GSIE] (IRQs *20)
[    0.557939] ACPI: PCI Interrupt Link [GSIF] (IRQs *21)
[    0.558945] ACPI: PCI Interrupt Link [GSIG] (IRQs *22)
[    0.560031] ACPI: PCI Interrupt Link [GSIH] (IRQs *23)
[    0.561293] ACPI: Enabled 2 GPEs in block 00 to 3F
[    0.562403] vgaarb: loaded
[    0.563177] SCSI subsystem initialized
[    0.564275] pps_core: LinuxPPS API ver. 1 registered
[    0.566211] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti<EMAIL_ADDRESS>[    0.569774] PTP clock support registered
[    0.571604] PCI: Using ACPI for IRQ routing
[    0.690721] clocksource: Switched to clocksource kvm-clock
[    0.709427] AppArmor: AppArmor Filesystem Enabled
[    0.711245] pnp: PnP ACPI init
[    0.712750] system 00:04: [mem 0xb0000000-0xbfffffff window] has been reserved
[    0.715761] pnp: PnP ACPI: found 5 devices
[    0.725735] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns:<PHONE_NUMBER> ns
[    0.729402] NET: Registered protocol family 2
[    0.731156] IP idents hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.736005] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
[    0.738688] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[    0.741283] TCP: Hash tables configured (established 65536 bind 65536)
[    0.743680] UDP hash table entries: 4096 (order: 5, 131072 bytes)
[    0.745599] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
[    0.747852] NET: Registered protocol family 1
[    0.904577] Trying to unpack rootfs image as initramfs...
[    2.051543] decompress cpio completed and skip redundant lzma
[    2.054778] Freeing initrd memory: 5564K
[    2.055660] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    2.056988] software IO TLB: mapped [mem 0x7ba55000-0x7fa55000] (64MB)
[    2.059448] audit: initializing netlink subsys (disabled)
[    2.061631] audit: type=2000 audit(1733079640.961:1): initialized
[    2.064352] Initialise system trusted keyring
[    2.084581] VFS: Disk quotas dquot_6.6.0
[    2.085916] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    2.090134] Key type asymmetric registered
[    2.091426] Asymmetric key parser 'x509' registered
[    2.092946] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    2.095125] io scheduler noop registered (default)
[    2.096736] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[    2.098407] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[    2.315055] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    2.343685] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[    2.620021] brd: module loaded
[    2.620976] lpc_ich 0000:00:1f.0: I/O space for GPIO uninitialized
[    2.622331] Loading iSCSI transport class v2.0-870.
[    2.629178] rdac: device handler registered
[    2.639893] ACPI: PCI Interrupt Link [GSIA] enabled at IRQ 16
[    2.642027] ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 6 ports 1.5 Gbps 0x3f impl SATA mode
[    2.643688] ahci 0000:00:1f.2: flags: 64bit ncq only
[    2.669799] scsi host0: ahci
[    2.688140] scsi host1: ahci
[    2.701551] scsi host2: ahci
[    2.709312] scsi host3: ahci
[    2.714745] scsi host4: ahci
[    2.719154] scsi host5: ahci
[    2.719918] ata1: SATA max UDMA/133 abar m4096@0xfebff000 port 0xfebff100 irq 24
[    2.721458] ata2: SATA max UDMA/133 abar m4096@0xfebff000 port 0xfebff180 irq 24
[    2.723002] ata3: SATA max UDMA/133 abar m4096@0xfebff000 port 0xfebff200 irq 24
[    2.724558] ata4: SATA max UDMA/133 abar m4096@0xfebff000 port 0xfebff280 irq 24
[    2.726101] ata5: SATA max UDMA/133 abar m4096@0xfebff000 port 0xfebff300 irq 24
[    2.727632] ata6: SATA max UDMA/133 abar m4096@0xfebff000 port 0xfebff380 irq 24
[    2.729277] rtc_cmos 00:03: RTC can wake from S4
[    2.730856] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[    2.732214] rtc_cmos 00:03: alarms up to one day, y3k, 242 bytes nvram
[    2.733553] i2c /dev entries driver
[    2.734364] md: raid1 personality registered for level 1
[    2.735566] NET: Registered protocol family 17
[    2.736514] Key type dns_resolver registered
[    2.739019] mce: Using 10 MCE banks
[    2.740134] registered taskstats version 1
[    2.740980] Loading compiled-in untrusted X.509 certificates
[    2.742122] Loading compiled-in X.509 certificates
[    2.743109] Loaded X.509 cert 'Synology SDG kernel module signing key: 7bd0b0d6bcd31651c22ce3978bdc8c8bdc417329'
[    2.749103] Loaded X.509 cert 'Synology Root Certification Authority: f2c075361f168425f8b5ef31b796406c3aab2089'
[    2.751118] Loaded X.509 cert 'Synology Kernel Module Signing Certification Authority: 600839b5d127e0e11d817a31f0575d323a7c0e28'
[    2.753435] Loaded X.509 cert 'Synology kernel module signing key: 4646ce54489669338118a3b1286da156ac366fa5'
[    2.755425] page_owner is disabled
[    2.756156] AppArmor: AppArmor sha1 policy hashing enabled
[    2.758428] rtc_cmos 00:03: setting system clock to 2024-12-01 19:00:38 UTC<PHONE_NUMBER>)
[    3.039961] ata3: SATA link down (SStatus 0 SControl 300)
[    3.041862] ata5: SATA link down (SStatus 0 SControl 300)
[    3.043670] ata1: SATA link down (SStatus 0 SControl 300)
[    3.045888] ata2: SATA link down (SStatus 0 SControl 300)
[    3.048322] ata4: SATA link down (SStatus 0 SControl 300)
[    3.050266] ata6: SATA link down (SStatus 0 SControl 300)
[    3.054793] Freeing unused kernel memory: 1008K
[    3.056369] Write protecting the kernel read-only data: 8192k
[    3.059399] Freeing unused kernel memory: 700K
[    3.062265] Freeing unused kernel memory: 336K
[    3.063930] tsc: Refined TSC clocksource calibration: 2197.478 MHz
[    3.065905] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x1face48cc96, max_idle_ns:<PHONE_NUMBER>99 ns
START /linuxrc.syno
START /linuxrc.syno.impl
[    3.271718] random: nonblocking pool is initialized
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore[    3.376617] ACPI: bus type USB registered
[    3.378203] usbcore: registered new interface driver usbfs
[    3.380271] usbcore: registered new interface driver hub
[    3.382285] usbcore: registered new interface driver ethub
[    3.384526] usbcore: registered new device driver usb
... [  OK  ]
:: Loading module ehci-hcd[    3.405688] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
... [  OK  ]
:: Loading module ehci-pci[    3.422396] ehci-pci: EHCI PCI platform driver
... [  OK  ]
:: Loading [    3.431908] uhci_hcd: USB Universal Host Controller Interface driver
module uhci-hcd ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
[    3.460283] kvmx64_synobios: loading out-of-tree module taints kernel.
[    3.462156] synobios ioctl TCGETS /dev/ttyS1 failed
[    3.463246] synobios unable to set termios of /dev/ttyS1
[    3.464777] 2024-12-1 19:0:39 UTC
[    3.465506] synobios: load, major number 201
[    3.466428] Brand: Synology
[    3.467056] Model: VirtualDSM
[    3.467727] set group disks wakeup number to 4, spinup time deno 7
[    3.469091] synobios cpu_arch proc entry initialized
[    3.470177] synobios crypto_hw proc entry initialized
[    3.471281] synobios syno_platform proc entry initialized
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocf[    3.480588] Module [kvmx64_synobios] is removed.
[    3.481688] synobios: unload
gen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
[    3.545176] ACPI: PCI Interrupt Link [GSIF] enabled at IRQ 21
[    3.550222] ACPI: PCI Interrupt Link [GSIH] enabled at IRQ 23
[    3.554352] ACPI: PCI Interrupt Link [GSIE] enabled at IRQ 20
[    3.558369] ACPI: PCI Interrupt Link [GSIG] enabled at IRQ 22
[    3.590393] scsi host6: Virtio SCSI HBA
[    3.604227] scsi 6:0:0:0: Direct-Access     QEMU     QEMU HARDDISK            2.5+ PQ: 0 ANSI: 5
[    3.607131] sd 6:0:0:0: [synoboot] 225280 512-byte logical blocks: (115 MB/110 MiB)
[    3.609356] sd 6:0:0:0: [synoboot] Write Protect is off
[    3.610760] sd 6:0:0:0: [synoboot] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.614347]  synoboot: synoboot1 synoboot2
[    3.623319] sd 6:0:0:0: [synoboot] Attached SCSI disk
[    6.599137] scsi host7: Virtio SCSI HBA
[    6.612626] scsi 7:0:0:0: Direct-Access     QEMU     QEMU HARDDISK            2.5+ PQ: 0 ANSI: 5
[    6.617034] sd 7:0:0:0: [sda] 20973568 512-byte logical blocks: (10.7 GB/10.0 GiB)
[    6.619785] sd 7:0:0:0: [sda] Write Protect is off
[    6.621428] sd 7:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    6.626566]  sda: sda1 sda2
[    6.642830] sd 7:0:0:0: [sda] Attached SCSI disk
[    9.560171] scsi host8: Virtio SCSI HBA
[    9.574547] scsi 8:0:0:0: Direct-Access     QEMU     QEMU HARDDISK            2.5+ PQ: 0 ANSI: 5
[    9.579221] sd 8:0:0:0: [sdb] 33554432 512-byte logical blocks: (17.2 GB/16.0 GiB)
[    9.582638] sd 8:0:0:0: [sdb] Write Protect is off
[    9.585283] sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    9.645899]  sdb: sdb1
[    9.683026] sd 8:0:0:0: [sdb] Attached SCSI disk
[   12.306254] scsi host9: Virtio SCSI HBA
[   12.320228] scsi 9:0:0:0: Direct-Access     QEMU     QEMU HARDDISK            2.5+ PQ: 0 ANSI: 5
[   12.324233] sd 9:0:0:0: [sdc]<PHONE_NUMBER>4 512-byte logical blocks: (11.5 TB/10.5 TiB)
[   12.329420] sd 9:0:0:0: [sdc] Write Protect is off
[   12.333314] sd 9:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   12.378062]  sdc: sdc1
[   12.409007] sd 9:0:0:0: [sdc] Attached SCSI disk
Partition Version=0
Partition layout is not DiskStation style. Skip checking rootfs.
ForceNewestLayout: Skipped
[   15.299349] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
[   15.322372] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Mounting /dev/sda1 /tmpRoot
[   15.380822] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
[   15.386608] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: barrier=1
cat: can't open '/tmp/fsck.root.log': No such file or directory
------------upgrade
Begin upgrade procedure
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck: No such file or directory while trying to open /dev/sda3
mount: mounting /dev/sda3 on /tmpData failed: No such file or directory
umount: can't unmount /tmpData: Invalid argument
[   15.663831] loop: module loaded
Failed to found any patch
No upgrade file found
End upgrade procedure
============upgrade
------------bootup-smallupdate
mkdir: can't create directory '/tmpRoot/proc': File exists
mkdir: can't create directory '/tmpRoot/sys': File exists
mkdir: can't create directory '/tmpRoot/dev': File exists
Try bootup smallupdate
No patch exist. Skip Packed Bootup SmallUpdate
Sparse files don't exist. Skip Sparse Bootup SmallUpdate
Finished synoautonano
============bootup-smallupdate
Wait 2 seconds for synology manufactory device
Sun Dec  1 19:00:56 UTC 2024
/dev/sda1 /tmpRoot ext4 rw,noatime,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
root: Start backing up logs in junior mode
[   21.009591] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
[   21.016082] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
umount: /etc/mtab: No such file or directory
linuxrc.syno executed successfully.
Post init
[   21.234481] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
[   21.240308] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: barrier=1
[   21.695923] systemd[1]: systemd 219 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR -SMACK +SYSVINIT -UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS -ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
[   21.704736] systemd[1]: Detected virtualization kvm.
[   21.706545] systemd[1]: Detected architecture x86-64.
Welcome to Linux!
[   21.710767] systemd[1]: Set hostname to .
[   24.909631] systemd[1]: Cannot add dependency job for unit kmip-server.service, ignoring: Unit kmip-server.service is masked.
[   24.913736] systemd[1]: Cannot add dependency job for unit synoperfeventd.service, ignoring: Unit synoperfeventd.service is masked.
[   24.917646] systemd[1]: Cannot add dependency job for unit pkg-install-low-priority-builtin.service, ignoring: Unit pkg-install-low-priority-builtin.service failed to load: No such file or directory.
[   24.923221] systemd[1]: Cannot add dependency job for unit pkg-synorelayd-reload-fixed-package-config.service, ignoring: Unit synorelayd.service failed to load: No such file or directory.
[   24.928170] systemd[1]: Cannot add dependency job for unit pkg-synorelayd-reload-package-config.service, ignoring: Unit synorelayd.service failed to load: No such file or directory.
[   24.932922] systemd[1]: Cannot add dependency job for unit pkg-install-high-priority-builtin.service, ignoring: Unit pkg-install-high-priority-builtin.service failed to load: No such file or directory.
[   24.937964] systemd[1]: Cannot add dependency job for unit SynoLedBrightness.service, ignoring: Unit SynoLedBrightness.service is masked.
[ INFO ] dev-hvc0.device is not active.
[DEPEND] Dependency failed for agetty for console output([   24.946368] systemd[1]: Dependency failed for agetty for console output(for vDSM).
for vDSM).
[   24.948864] systemd[1]: Job vdsm_dummy_tty.service/start failed with result 'dependency'.
[  OK  ] Reached target Swap.
[   24.953095] systemd[1]: Reached target Swap.
[   24.954805] systemd[1]: Starting Swap.
[  OK  ] Created slice Root Slice.
[   24.958913] systemd[1]: Created slice Root Slice.
[   24.960788] systemd[1]: Starting Root Slice.
[  OK  ] Created slice ScsiTarget's slice.
[   24.964510] systemd[1]: Created slice ScsiTarget's slice.
[   24.966744] systemd[1]: Starting ScsiTarget's slice.
[  OK  ] Created slice OAuthService's slice.
[   24.970942] systemd[1]: Created slice OAuthService's slice.
[   24.973183] systemd[1]: Starting OAuthService's slice.
[  OK  ] Created slice SNMP.
[   24.977057] systemd[1]: Created slice SNMP.
[   24.978413] systemd[1]: Starting SNMP.
[  OK  ] Created slice RAID Resync Proces[   24.981657] systemd[1]: Created slice RAID Resync Process. Including Resync, Repair and Reshape..
s. ...ing Resync[   24.984453] systemd[1]: Starting RAID Resync Process. Including Resync, Repair and Reshape..
, Repair and Reshape..
[  [   24.988332] systemd[1]: Created slice OpenBSD Secure Shell server.
OK  ] Create[   24.990744] systemd[1]: Starting OpenBSD Secure Shell server.
d slice OpenBSD Secure Shell ser[   24.993666] systemd[1]: Created slice VirtualDSM daemon slice.
ver.
[  OK[   24.995845] systemd[1]: Starting VirtualDSM daemon slice.
] Created slice VirtualDSM[   24.998112] systemd[1]: Created slice QuickConnect's slice.
daemon slice.
[   25.000010] systemd[1]: Starting QuickConnect's slice.
[  OK  ] Created slice [   25.002047] systemd[1]: Created slice Package Center Slice.
QuickConnect's s[   25.003839] systemd[1]: Starting Package Center Slice.
lice.
[  OK  ] Created[   25.006190] systemd[1]: Created slice Synology DSM internal service.
slice Package C[   25.008172] systemd[1]: Starting Synology DSM internal service.
enter Slice.
[  OK  ] [   25.010528] systemd[1]: Created slice SynoFinder's slice.
Created slice Sy[   25.012136] systemd[1]: Starting SynoFinder's slice.
nology DSM internal service.
[ systemd[1]: Created slice Synology Flashcache.
[32m  OK  ] [   25.016011] systemd[1]: Starting Synology Flashcache.
Created slice Sy[   25.018027] systemd[1]: Created slice BTRFS Space Reclaim.
noFinder's slice[   25.019321] systemd[1]: Starting BTRFS Space Reclaim.
.
[  OK  ] Created sli[   25.021283] systemd[1]: Created slice synobackup daemon slice.
ce Synology Flas[   25.023069] systemd[1]: Starting synobackup daemon slice.
hcache.
[  OK  ] Creat[   25.025138] systemd[1]: Created slice Synology Index slice (WAT).
ed slice BTRFS S[   25.026761] systemd[1]: Starting Synology Index slice (WAT).
pace Reclaim.
[  OK  ][   25.028581] systemd[1]: Listening on Journal Audit Socket.
Created slice s[   25.030039] systemd[1]: Starting Journal Audit Socket.
ynobackup daemon slice.
[  OK  ] Creat[   25.031975] systemd[1]: Created slice BTRFS Optimization.
ed slice Synolog[   25.033411] systemd[1]: Starting BTRFS Optimization.
y Index slice (WAT).
[  OK[   25.035053] systemd[1]: Listening on Journal Socket.
] Listenin[   25.036458] systemd[1]: Starting Journal Socket.
g on Journal Audit Socket.
[   25.037967] systemd[1]: Created slice ActiveBackup-Office365's slice.
2m  OK  ] Cr[   25.039639] systemd[1]: Starting ActiveBackup-Office365's slice.
[   25.041505] systemd[1]: Created slice FileStation's slice.
[  OK     25.042968] systemd[1]: Starting FileStation's slice.
m] Listening on Journal Socket.
[  OK  ] Created slice ActiveBackup-Office365's slice.
[  OK  ] Created slice FileStation's slice.
[   25.056899] systemd[1]: Starting Synology Plugin Daemon...
Starting Synology Plugin Daemon...
[  OK  ] Listening on udev Control Socket.
[   25.060226] systemd[1]: Listening on udev Control Socket.
[   25.061472] systemd[1]: Starting udev Control Socket.
[  OK  ] Reached target Paths.
[   25.063726] systemd[1]: Reached target Paths.
[   25.064718] systemd[1]: Starting Paths.
[  OK  ] Created slice SupportService's slice.
[   25.067109] systemd[1]: Created slice SupportService's slice.
[   25.068393] systemd[1]: Starting SupportService's slice.
[  OK  ] Created slice Synology DSM Storage Service.
[   25.070767] systemd[1]: Created slice Synology DSM Storage Service.
[   25.072362] systemd[1]: Starting Synology DSM Storage Service.
[  OK  ] Created slice Task Scheduler Group.
[   25.075064] systemd[1]: Created slice Task Scheduler Group.
[   25.076295] systemd[1]: Starting Task Scheduler Group.
[  OK  ] Created slice Python2's slice.
[   25.078900] systemd[1]: Created slice Python2's slice.
[   25.080058] systemd[1]: Starting Python2's slice.
[  OK  ] Created slice SMBService's slice.
[   25.082239] systemd[1]: Created slice SMBService's slice.
[   25.083480] systemd[1]: Starting SMBService's slice.
[  OK  ] Listening on udev Kernel Socket.
[   25.085877] systemd[1]: Listening on udev Kernel Socket.
[   25.087058] systemd[1]: Starting udev Kernel Socket.
[  OK  ] Created slice Synology Cache Advisor.
[   25.089379] systemd[1]: Created slice Synology Cache Advisor.
[   25.090773] systemd[1]: Starting Synology Cache Advisor.
[  OK  ] Created slice Synology DSM desktop service.
[   25.093140] systemd[1]: Created slice Synology DSM desktop service.
[   25.094724] systemd[1]: Starting Synology DSM desktop service.
[  OK  ] Created slice SecureSignIn's slice.
[   25.097672] systemd[1]: Created slice SecureSignIn's slice.
[   25.099957] systemd[1]: Starting SecureSignIn's slice.
[  OK  ] Created slice Synology Swap Works.
[   25.103736] systemd[1]: Created slice Synology Swap Works.
[   25.105921] systemd[1]: Starting Synology Swap Works.
[  OK  ] Created slice TextEditor's slice.
[   25.109526] systemd[1]: Created slice TextEditor's slice.
[   25.111508] systemd[1]: Starting TextEditor's slice.
[  OK  ] Created slice System Slice.
[   25.115122] systemd[1]: Created slice System Slice.
[   25.116833] systemd[1]: Starting System Slice.
[  OK  ] Created slice system-syno\x2dmd\x2dresync\x2dspeed\x2dadjust.sli[   25.120003] systemd[1]: Created slice system-syno\x2dmd\x2dresync\x2dspeed\x2dadjust.slice.
ce.
[   25.122839] systemd[1]: Starting system-syno\x2dmd\x2dresync\x2dspeed\x2dadjust.slice.
[   25.130909] systemd[1]: Mounting Debug File System...
Mounting Debug File System...
[   25.135389] systemd[1]: Starting Load ntb_brd module...
Starting Load ntb_brd module...
[   25.140102] systemd[1]: Starting Synology swap...
Starting Synology swap...
[   25.144341] systemd[1]: Starting Link coredump path to volume if possible...
Starting Link coredump path to volume if possibl[   25.147392] systemd[1]: Started Set project quota ID for /var/log.
e...
[   25.150125] systemd[1]: Starting check integrity of rd.gz decompression...
Starting check integrity of rd.gz decompression...
[  OK  [   25.153518] systemd[1]: Created slice system-serial\x2dgetty.slice.
] Created sl[   25.155560] systemd[1]: Starting system-serial\x2dgetty.slice.
ice system-serial\x2dgetty.slice[   25.158118] systemd[1]: Starting Set hostname...
.
Starting Set hostname...
[   25.161391] systemd[1]: Starting Disabling fan checking flag ......
Starting Disabling fan checking flag ......
[   25.175904] systemd[1]: Starting Load Kernel Modules...
Starting Load Kernel Modules...
[   25.178791] systemd[1]: Starting unbind USB device...
Starting unbind USB device...
[   25.181466] systemd[1]: Starting Set boot sequence config...
Starting Set boot sequence config...
[   25.184518] systemd[1]: Starting Set time zone information to kernel...
Starting Set time zone information to kernel...
[  OK  ] Created slice scemd.
[   25.188406] systemd[1]: Created slice scemd.
[   25.189414] systemd[1]: Starting scemd.
[   25.191179] systemd[1]: Mounting Temporary Directory...
Mounting Temporary Directory...
[  OK  ] Reached target Timers.
[   25.194275] systemd[1]: Reached target Timers.
[   25.195304] systemd[1]: Starting Timers.
[  OK  ] Created slice Shared Folder Sync.
[   25.197541] systemd[1]: Created slice Shared Folder Sync.
[   25.198787] systemd[1]: Starting Shared Folder Sync.
[   25.200542] systemd[1]: Starting Journal Socket (/dev/log).
[  OK  ] Created slice User and Session Slice.
[   25.203332] systemd[1]: Created slice User and Session Slice.
[   25.204692] systemd[1]: Starting User and Session Slice.
[  OK  ] Reached target Slices.
[   25.206928] systemd[1]: Reached target Slices.
[   25.208002] systemd[1]: Starting Slices.
[  OK  ] Created slice StorageManager's slice.
[   25.210553] systemd[1]: Created slice StorageManager's slice.
[   25.212019] systemd[1]: Starting StorageManager's slice.
[  OK  ] Mounted Debug File System.
[   25.215185] systemd[1]: Mounted Debug File System.
[  OK  ] Mounted Temporary Directory.
[   25.217412] systemd[1]: Mounted Temporary Directory.
[  OK  ] Started Synology Plugin Daemon.
[   25.220148] systemd[1]: Started Synology Plugin Daemon.
[  OK  ] Started Load ntb_brd module.
[   25.223121] systemd[1]: Started Load ntb_brd module.
[  OK  ] Started Set hostname.
[   25.225507] systemd[1]: Started Set hostname.
[  OK  ] Started Disabling fan checking flag ....
[   25.228286] systemd[1]: Started Disabling fan checking flag ....
[  OK  ] Started unbind USB device.
[   25.231428] systemd[1]: Started unbind USB device.
[  OK  ] Started Set boot sequence config.
[   25.234901] systemd[1]: Started Set boot sequence config.
[  OK  ] Started check integrity of rd.gz decompression.
[   25.238270] systemd[1]: Started check integrity of rd.gz decompression.
[  OK  ] Started Set time zone information to kernel.
[   25.241864] systemd[1]: Started Set time zone information to kernel.
[  OK  ] Listening on Journal Socket (/dev/log).
[   25.244775] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Reached target Sockets.
[   25.247197] systemd[1]: Reached target Sockets.
[   25.248304] systemd[1]: Starting Sockets.
[   25.250179] systemd[1]: Starting Journal Service...
Starting Journal Service...
[  OK  ] Reached target Local File Systems.
[   25.253680] systemd[1]: Reached target Local File Systems.
[   25.254970] systemd[1]: Starting Local File Systems.
[   25.256809] systemd[1]: Starting udev Coldplug all Devices...
Starting udev Coldplug all Devices...
[   25.259745] systemd[1]: Starting D-Bus Session Message Bus...
Starting D-Bus Session Message Bus...
[   25.263033] systemd[1]: Starting Set boot sequence config for temporary use...
Starting Set boot sequence config for temporary use...
[   25.266468] systemd[1]: Starting D-Bus System Message Bus...
Starting D-Bus System Message Bu[   25.276274] zram: Added device: zram0
s...
[   25.278278] zram: Added device: zram1
[   25.280031] systemd[1]: Starting Mount efivarfs...
[   25.280147] zram: Added device: zram2
[   25.280489] zram: Added device: zram3
Starting Mount efivarfs...
[   25.285920] systemd[1]: Starting Mount usb fs...
Starting Mount usb fs...
[  OK  ] Started Link coredump path to volume if possible.
[   25.293416] systemd[1]: Started Link coredump path to volume if possible.
[  OK  ] Started Set boot sequence config for temporary use.
[   25.298678] systemd[1]: Started Set boot sequence config for temporary use.
[  OK  ] Started Mount efivarfs.
[   25.303091] systemd[1]: Started Mount efivarfs.
[  OK  ] Started Journal Service.
[   25.305843] systemd[1]: Started Journal Service.
Starting Flush Journal to Persistent Storage...
Starting System Logger Daemon...
[   25.335929] Adding 2097148k swap on /dev/sda2.  Priority:-1 extents:1 across:2097148k SS
[   25.341949] zram0: detected capacity change from 0 to<PHONE_NUMBER>
[   25.349670] Adding 1225724k swap on /dev/zram0.  Priority:1 extents:1 across:1225724k SS
[   25.355544] zram1: detected capacity change from 0 to<PHONE_NUMBER>
[   25.361505] Adding 1225724k swap on /dev/zram1.  Priority:1 extents:1 across:1225724k SS
[   25.366821] zram2: detected capacity change from 0 to<PHONE_NUMBER>
[   25.372552] Adding 1225724k swap on /dev/zram2.  Priority:1 extents:1 across:1225724k SS
[FAILED] Failed to start Mount usb fs.
See "systemctl status syno-mount-usbfs.service" for details.
[   25.379859] zram3: detected capacity change from 0 to<PHONE_NUMBER>
[   25.386584] Adding 1225724k swap on /dev/zram3.  Priority:1 extents:1 across:1225724k SS
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started Synology swap.
[   25.393646] systemd-journald[6037]: Received request to flush runtime journal from PID 1
[  OK  ] Started Flush Journal to Persistent Storage.
Starting Create Volatile Files and Directories...
[  OK  ] Started D-Bus Session Message Bus.
[  OK  ] Started D-Bus System Message Bus.
Starting Synology Network Daemon...
[   25.528179] NET: Registered protocol family 10
[   25.572949] sit: IPv6 over IPv4 tunneling driver
[  OK  ] Started Create Volatile Files and Directories.
Starting synodsmnotify...
[  OK  ] Reached target Create SDK locks directory.
Starting Check Synology user info consistency...
Starting Check /etc/synoinfo.conf...
Starting Check Synology group info consistency...
Starting Synology Database Update...
[  OK  ] Started synodsmnotify.
[   25.689517] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised<EMAIL_ADDRESS>[  OK  ] Started Synology Database Update.
[   25.742584] sd 6:0:0:0: Attached scsi generic sg0 type 0
[   25.744599] sd 7:0:0:0: Attached scsi generic sg1 type 0
[   25.746905] sd 8:0:0:0: Attached scsi generic sg2 type 0
[   25.749227] sd 9:0:0:0: Attached scsi generic sg3 type 0
[  OK  ] Started Check /etc/synoinfo.conf.
[   25.846358] qed_init called
[   25.847479] QLogic FastLinQ 4xxxx Core Module qed <IP_ADDRESS>
[   25.849501] creating debugfs root node
[   25.868216] qede_init: QLogic FastLinQ 4xxxx Ethernet Driver qede <IP_ADDRESS>
[  OK  ] Started Synology Network Daemon.
Starting Wait for synonetd ready...
[  OK  ] Started Wait for synonetd ready.
Starting Synology Network Event Daemon...
[  OK  ] Started Synology Network Event Daemon.
[  OK  ] Started Check Synology user info consistency.
[   26.103192] i40evf: Intel(R) 40-10 Gigabit Virtual Function Network Driver - version 3.6.15
[   26.105383] Copyright(c) 2013 - 2018 Intel Corporation.
[   26.117365] igbvf: Intel(R) Gigabit Virtual Function Driver - <IP_ADDRESS>
[   26.120425] igbvf: Copyright (c) 1999-2015 Intel Corporation.
[   26.145500] ixgbevf: Intel(R) 10GbE PCI Express Virtual Function Driver - version 4.5.3
[   26.148727] Copyright(c) 1999 - 2019 Intel Corporation.
[  OK  ] Started Check Synology group info consistency.
[  OK  ] Started Load Kernel Modules.
Starting Load Fan Modules in Kernel Project...
Starting Apply default and user cus... sysctl.conf kernel variable....
Starting Load Kernel Modules in Kernel Project...
Mounting Configuration File System...
Starting Adjust NIC sequence...
[  OK  ] Reached target Synology local user and group ready.
Starting Synology Task Scheduler Init...
[  OK  ] Reached target User and Group Name Lookups.
[  OK  ] Mounted Configuration File System.
[  OK  ] Started Load Fan Modules in Kernel Project.
[   26.194514] usbcore: registered new interface driver usblp
[  OK  ] Started Apply default and user cust...ed sysctl.conf kernel variable..
Starting Apply Kernel Variables...
[FAILED] Failed to start Adjust NIC sequence.
See "systemctl status SynoInitEth.service" for details.
[   26.233538] usbcore: registered new interface driver usbhid
[   26.235222] usbhid: USB HID core driver
[  OK  ] Started Apply Kernel Variables.
Starting Apply kernel variable vm.kswapd_threads...
Starting Apply kernel variable kernel-shmmni at least 16384...
Starting Adjust kernel parameters -...or, vm.watermark_boost_factor...
Starting Apply kernel variable kernel.sem at least 1024...
[  OK  ] Started Apply kernel variable vm.kswapd_threads.
[   26.292019] synobios ioctl TCGETS /dev/ttyS1 failed
[   26.293729] synobios unable to set termios of /dev/ttyS1
[[   26.296136] 2024-12-1 19:1:1 UTC
OK  [   26.297206] synobios: load, major number 201
[   26.298930] Brand: Synology
[   26.299964] Model: VirtualDSM
] [   26.300943] set group disks wakeup number to 4, spinup time deno 7
[   26.303016] synobios cpu_arch proc entry initialized
[   26.304805] synobios crypto_hw proc entry initialized
Started Apply ke[   26.306529] synobios syno_platform proc entry initialized
rnel variable kernel-shmmni at least 16384.
[   26.425762] AVX2 version of gcm_enc/dec engaged.
[   26.427687] AES CTR mode by8 optimization enabled
[  OK  ] Started Synology Task Scheduler Init.
[   26.479620] usbcore: registered new interface driver usb-storage
[  OK  ] Started Load Kernel Modules in Kernel Project.
Starting Software Init Led for support led v2 models...
Starting DSM Release Rolling Group ID...
[  OK  ] Started Apply kernel variable kernel.sem at least 1024.
[  OK  ] Started Adjust kernel parameters - ...ctor, vm.watermark_boost_factor.
[  OK  ] Started DSM Release Rolling Group ID.
[  OK  ] Started Software Init Led for support led v2 models.
[  OK  ] Started System Logger Daemon.
Starting synodrnode...
[  OK  ] Reached target Synology Task Schedu...brary functions and tasks ready.
[DEPEND] Dependency failed for rebuild local user and group db.
Starting Synology Log bootup start...
[  OK  ] Reached target Synology root filesystem (rw) ready.
[  OK  ] Reached target Network (Pre).
Starting Umount initrd...
Starting Load AppArmor profiles...
Starting DSM Installation ID...
Starting Clean UPS config...
Starting Set Eunit Sequence...
Starting Set arp ignore...
Starting Synology check locale...
Starting DSM Boot Health Check...
Starting syno-cgi-keygen.service...
Starting Synology Default TLS Profile...
[  OK  ] Started Clean UPS config.
[  OK  ] Started Set Eunit Sequence.
Starting udev Kernel Device Manager...
[  OK  ] Started Set arp ignore.
Starting rc.network...
[  OK  ] Started Synology check locale.
[  OK  ] Started DSM Installation ID.
[  OK  ] Started Umount initrd.
[  OK  ] Started Synology Default TLS Profile.
[  OK  ] Started Synology Log bootup start.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started synodrnode.
[  OK  ] Found device /dev/synoboot2.
[  OK  ] Reached target Synology synoboot2 done.
[  OK  ] Started DSM Boot Health Check.
[  OK  ] Started syno-cgi-keygen.service.
[   29.258784] 8021q: 802.1Q VLAN Support v1.8
[   29.260553] 8021q: adding VLAN 0 to HW filter on device eth0
Starting DHCP client init...
[  OK  ] Created slice system-dhclient.slice.
[  OK  ] Started DHCP client init.
Starting eth0 DHCP Client...
[  OK  ] Started eth0 DHCP Client.
[  OK  ] Started rc.network.
[  OK  ] Reached target Network.
Starting PPPoE...
Starting Check if network is ready...
[  OK  ] Started PPPoE.
[  OK  ] Started Load AppArmor profiles.
[  OK  ] Reached target System Initialization.
Starting bootup upgrade sha package...
[  OK  ] Started Synology token manager.
Starting Synology token manager...
[  OK  ] Started Synology task manager.
Starting Synology task manager...
[  OK  ] Started Serial Getty on ttyS0.
Starting Serial Getty on ttyS0...
[  OK  ] Reached target Login Prompts.
[  OK  ] Started bootup upgrade sha package.
[  OK  ] Reached target Basic System.
Starting Synology SCGI SocketIO...
Starting Samba Environment Setup Unit...
Starting synology volume encryption get machine key service...
Starting always preprocess jobs before any package is started...
Starting Service for irq balance...
Starting OpenBSD Secure Shell server...
Starting System Profile Tuning...
Starting Prepare notification cache data...
Starting Samba Unlinkd Daemon...
Starting Redis data structure server for webapi...
[  OK  ] Started synobackup daemon.
Starting synobackup daemon...
Starting Synology guest command handle daemon...
Starting synoconfd daemon...
Starting Log Rotate Daemon...
Starting Login Service...
Starting Synology Schedule Daemon...
[  OK  ] Started Synology log accounting service.
Starting Synology log accounting service...
Starting findhost daemon...
Starting Control RC power...
Starting Synology guest service daemon...
Starting Synology firmware DLMC...
Starting Hibernation debug check...
Starting Synology filesytem check on bootup...
Starting Synology log notification service...
Starting WD idle3 timer...
Starting synocontentextract gen INFO file for synoindex...
[  OK  ] Started Check if network is ready.
[  OK  ] Started synology volume encryption get machine key service.
[  OK  ] Started Synology firmware DLMC.
[  OK  ] Started Synology filesytem check on bootup.
[  OK  ] Started WD idle3 timer.
Starting Synology space service...
[  OK  ] Reached target Network is Online.
Starting VPN Client...
Starting Traffic Control...
Starting Entry for WS-Transfer and WS-Discovery Server...
Starting NTP client/server...
Starting broadcast synorelayd boot state...
Starting register ds region by ip...
Starting Set Policy Route...
[  OK  ] Started Service for irq balance.
[  OK  ] Started Synology Schedule Daemon.
[  OK  ] Started Synology guest service daemon.
[  OK  ] Started synocontentextract gen INFO file for synoindex.
[  OK  ] Started synoconfd daemon.
Starting synoindex check if there a...ny synoindex-related packages...
Starting Synology guest communication daemon...
[  OK  ] Started Hibernation debug check.
[  OK  ] Started Entry for WS-Transfer and WS-Discovery Server.
[   30.150880] exdisplay_handler not implemented
[  OK  ] Started Control RC power.
[  OK  ] Started Login Service.
[  OK  ] Started OpenBSD Secure Shell server.
[  OK  ] Started System Profile Tuning.
[  OK  ] Started Samba Unlinkd Daemon.
[   30.281078] Synotify use 16384 event queue size
[  OK  ] Started Log Rotate Daemon.
[  OK  ] Started VPN Client.
[  OK  ] Started findhost daemon.
[  OK  ] Started always preprocess jobs before any package is started.
[  OK  ] Reached target Hook on root ready.
Starting QuickConnect's service unit...
Starting SMBService's service unit...
Starting Python2's service unit...
Starting SecureSignIn's service unit...
[  OK  ] Started Synology log notification service.
[  OK  ] Started Synology guest communication daemon.
[  OK  ] Started Redis data structure server for webapi.
[  OK  ] Started Synology SCGI.
Starting Synology SCGI...
[  OK  ] Stopped Synology Task Scheduler Vmtouch.
[  OK  ] Started Synology Task Scheduler Vmtouch.
Starting Synology Task Scheduler Vmtouch...
[  OK  ] Started Samba Environment Setup Unit.
Starting NetBIOS name server...
[  OK  ] Started Synology guest command handle daemon.
Starting Issue VDSM ready for intialization before boot-done....
[  OK  ] Started NTP client/server.
[  OK  ] Started Traffic Control.
[  OK  ] Started synoindex check if there are any synoindex-related packages.
Starting synoindex mediad...
[  OK  ] Started Issue VDSM ready for intialization before boot-done..
[  OK  ] Started broadcast synorelayd boot state.
[  OK  ] Started Set Policy Route.
[  OK  ] Started Prepare notification cache data.
[  OK  ] Started register ds region by ip.
Starting Run sysnotify migration sc... string and network are ready...
Stopping Synology Task Scheduler Vmtouch...
[  OK  ] Stopped Synology Task Scheduler Vmtouch.
[  OK  ] Started Synology Task Scheduler Vmtouch.
Starting Synology Task Scheduler Vmtouch...
[  OK  ] Started Run sysnotify migration scr...il string and network are ready.
[  OK  ] Started synoindex mediad.
Stopping Synology Task Scheduler Vmtouch...
[  OK  ] Stopped Synology Task Scheduler Vmtouch.
[  OK  ] Started Synology Task Scheduler Vmtouch.
Starting Synology Task Scheduler Vmtouch...
[  OK  ] Started Synology space service.
Starting Synology virtual space service...
[  OK  ] Started Synology virtual space service.
Starting Synology virtual space service phase2...
[  OK  ] Started Synology virtual space service phase2.
[  OK  ] Reached target Synology storage pool.
Starting StorageManager's service unit...
Starting Synology space table update for Storage Manager...
Starting Synology Building Tasks Restore for Storage Manager...
Starting Check Synology HotSpare Config...
Starting Synology filesystem check service...
[  OK  ] Started Synology Building Tasks Restore for Storage Manager.
[  OK  ] Started Synology filesystem check service.
Starting Synology volume service...
[   33.246731] raid6: sse2x1   gen()  5609 MB/s
[   33.264735] raid6: sse2x1   xor()  4408 MB/s
[   33.282728] raid6: sse2x2   gen()  8527 MB/s
[   33.300729] raid6: sse2x2   xor()  5861 MB/s
[   33.317730] raid6: sse2x4   gen() 10906 MB/s
[   33.334731] raid6: sse2x4   xor()  7080 MB/s
[   33.351725] raid6: avx2x1   gen() 15207 MB/s
[   33.368714] raid6: avx2x1   xor() 10240 MB/s
[   33.386715] raid6: avx2x2   gen() 17582 MB/s
[   33.403715] raid6: avx2x2   xor() 10601 MB/s
[   33.420772] raid6: avx2x4   gen() 20507 MB/s
[   33.438771] raid6: avx2x4   xor() 12917 MB/s
[   33.439753] raid6: using algorithm avx2x4 gen() 20507 MB/s
[   33.440976] raid6: .... xor() 12917 MB/s, rmw enabled
[   33.442104] raid6: using avx2x2 recovery algorithm
[   33.451129] xor: automatically using best checksumming function:
[   33.461715]    avx       : 22480.000 MB/sec
[  OK  ] Started Synology space table update for Storage Manager.
[  OK  ] Created slice SecureSignin.slice.
Starting Login Invoke Daemon...
[   33.621223] Btrfs loaded, crc32c=crc32c-intel
[  OK  ] Started Login Invoke Daemon.
[   33.787631] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
[  OK  ] Started NetBIOS name server.
[  OK  ] Started WS-Discovery Server.
Starting WS-Discovery Server...
[   34.023878] BTRFS: device label 2024.11.21-17:26:58 v72806 devid 1 transid 720 /dev/sdb1
[   34.027859] BTRFS info (device sdb1): enabling auto syno reclaim space
[   34.029592] BTRFS info (device sdb1): use ssd allocation scheme
[   34.031143] BTRFS info (device sdb1): turning on discard
[   34.032562] BTRFS info (device sdb1): using free space tree
[   34.034025] BTRFS info (device sdb1): using free block group cache tree
[   34.035777] BTRFS info (device sdb1): has skinny extents
[   34.036574] BTRFS: device label 2024.11.20-13:09:48 v72806 devid 1 transid 16179 /dev/sdc1
[  OK  [   34.040453] BTRFS info (device sdc1): enabling auto syno reclaim space
[   34.042113] BTRFS info (device sdc1): use ssd allocation scheme
] [   34.043488] BTRFS info (device sdc1): turning on discard
[   34.044730] BTRFS info (device sdc1): using free space tree
Started Check Sy[   34.045995] BTRFS info (device sdc1): using free block group cache tree
nology HotSpare [   34.047808] BTRFS info (device sdc1): has skinny extents
Config.
[  OK  ] Started SecureSignIn's service unit.
[   34.188554] BTRFS info (device sdb1): BTRFS: root of syno feature tree is null
[  OK  ] Started StorageManager's service[   34.257253] BTRFS info (device sdc1): BTRFS: root of syno feature tree is null
unit.
[  OK  ] Started Python2's service unit.
[  OK  ] Started SMBService's service unit.
Stopping Synology Task Scheduler Vmtouch...
[  OK  ] Stopped Synology Task Scheduler Vmtouch.
[  OK  ] Started Synology Task Scheduler Vmtouch.
Starting Synology Task Scheduler Vmtouch...
[  OK  ] Started Synology volume service.
Starting Synology volume mount post hook...
o365backup login: [   36.829859] Synotify use 16384 event queue size
[   36.830886] Synotify use 16384 event queue size
[   37.693124] capability: warning: `nginx' uses 32-bit capabilities (legacy support in use)
❯ -----------------------------------------------------------
❯  You can now login to DSM at http://<IP_ADDRESS>:5000
❯ -----------------------------------------------------------
[   39.473062] iSCSI:target_core_rodsp_server.c:1025:rodsp_server_init RODSP server started, login_key(26a4ffccd989).
[   39.503852] syno_extent_pool: module license 'Proprietary' taints kernel.
[   39.506192] Disabling lock debugging due to kernel taint
[   39.509448] iSCSI:extent_pool.c:766:ep_init syno_extent_pool successfully initialized
[   39.524309] iSCSI:target_core_device.c:612:se_dev_align_max_sectors Rounding down aligned max_sectors from<PHONE_NUMBER> to<PHONE_NUMBER>
[   39.527084] iSCSI:target_core_configfs.c:5763:target_init_dbroot db_root: cannot open: /etc/target
[   39.529778] iSCSI:target_core_lunbackup.c:366:init_io_buffer_head 2048 buffers allocated, total 8388608 bytes successfully
[   39.563896] iSCSI:target_core_file.c:152:fd_attach_hba RODSP plugin for fileio is enabled.
[   39.567195] iSCSI:target_core_file.c:159:fd_attach_hba ODX Token Manager is enabled.
[   39.570283] iSCSI:target_core_multi_file.c:91:fd_attach_hba RODSP plugin for multifile is enabled.
[   39.573851] iSCSI:target_core_ep.c:795:ep_attach_hba RODSP plugin for epio is enabled.
[   39.576975] iSCSI:target_core_ep.c:802:ep_attach_hba ODX Token Manager is enabled.
[   39.721894] workqueue: max_active 1024 requested for vhost_scsi is out of range, clamping between 1 and 512
[   41.225813] findhostd uses obsolete (PF_INET,SOCK_PACKET)
[   42.055958] fuse init (API version 7.23)
[   43.835316] Synotify use 16384 event queue size
Screenshots (optional)
No response

i'm used macvlan a few days/weeks and the container was healthy.....

this helped, container is healthy again. Thank you


no response format for cli calls anywhere in the docs

How are we supposed to find out the response format of cli call? Trial and error? Please generate docs from code.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c12e07f8-d82f-a9ac-895a-b6d980c8c4c2
Version Independent ID: 43924bb5-20bd-6a0e-9cdc-90b1db46e599
Content: az network public-ip
Content Source: latest/docs-ref-autogen/network/public-ip.yml
Service: virtual-network
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

cc @yonzhan since this is network command

@Morriz  Could you describe your question with more details?

Sure. The docs nicely describe input format, but no ouput format.

@Morriz Could you please share the doc link you mentioned?

I am talking about all your az cli documentation. All input parameters are always nicely given, and some examples. None give response formats, even though your docs mention to be "Azure CLI / Reference".
Sample links:

https://docs.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az_aks_create
https://docs.microsoft.com/en-us/cli/azure/keyvault?view=azure-cli-latest#az_keyvault_create

Nowhere do you provide response formats. Why?

@Morriz Format of input parameters are defined in https://github.com/Azure/azure-rest-api-specs, but most of response format is not defined in it. Usually we run the cmd in practical environment to get the response format. In the future we may think about to add it.

CLI doesn't explicitly document the response body, but you may refer to the document of underlying services.
Take ResourceGroup as an example, corresponding docs are

Azure REST spec - definition: ResourceGroup
Azure REST doc - HTTP request/response: Resource Groups - Get
Azure Python SDK - model: ResourceGroup
Azure CLI - command: az group show

The relationship between them are:

Azure REST spec describes Azure REST API of all services
Azure Python SDK is generated from Azure REST spec
Azure CLI uses Azure Python SDK to call Azure REST API

Therefore, the easiest way is to check Azure REST doc which should be consistent with Azure CLI's response.
⚠ The only thing you need to pay attention is that properties may be flattened by Azure CLI.
For example, az group show (internally calls Resource Groups - Get) returns a ResourceGroup with properties:
> az group show -n test
{
  "id": "/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/resourceGroups/test",
  "location": "westus",
  "managedBy": null,
  "name": "test",
  "properties": {
    "provisioningState": "Succeeded"
  },
  "tags": null,
  "type": "Microsoft.Resources/resourceGroups"
}

Meanwhile, az storage account show (internally calls Storage Accounts - Get Properties) returns a StorageAccount whose properties has been flattened by Azure CLI:
> az storage account show -n test
{
  "accessTier": "Hot",
  "allowBlobPublicAccess": null,
  "allowSharedKeyAccess": null,
  "azureFilesIdentityBasedAuthentication": null,
  ...
  "name": "test",
  "type": "Microsoft.Storage/storageAccounts"
}

The reason behind the flattening is because ResourceGroup's REST spec defines
https://github.com/Azure/azure-rest-api-specs/blob/e10fd5f5f0b3444e589cd816321fce7036e33554/specification/resources/resource-manager/Microsoft.Resources/stable/2020-10-01/resources.json#L5549-L5552
"properties": {
  "$ref": "#/definitions/ResourceGroupProperties",
  "description": "The resource group properties."
},

while StorageAccount's REST spec defines:
https://github.com/Azure/azure-rest-api-specs/blob/e10fd5f5f0b3444e589cd816321fce7036e33554/specification/storage/resource-manager/Microsoft.Storage/stable/2021-01-01/storage.json#L3083-L3087
"properties": {
  "x-ms-client-flatten": true,
  "$ref": "#/definitions/StorageAccountProperties",
  "description": "Properties of the storage account."
}

Azure Python SDK honors x-ms-client-flatten and flattens properties accordingly.

So can you see that it is confusing to NOT be given explicit response formats for each command?

Yes, I can see that. However, in short, it is hard.
Azure CLI is built on Python which is not a strong-typed language, so CLI is not aware of the type of the returned object from Python SDK forehandedly. Also, there is no 1:1 mapping between Azure CLI commands and SDK/REST APIs. (Yes, in most cases, one CLI command calls one REST API, but there are exceptions like az vm create which calls multiple REST APIs in one command.)
Well, I do agree that the response of Azure CLI should be consistent with REST API, but that is not the case due to x-ms-client-flatten. I have created https://github.com/Azure/azure-rest-api-specs/issues/13578 to track it. You may vote on that issue.
Then we should consider if we can link CLI commands to REST docs, because the responses are now unified.

That sounds like a good plan. I suggest to always link to the REST doc counterpart for now (with a warning about potential incongruence), assuming it is easy to put that link underneath a CLI page.


Create examples for the NSM custom resource

First of all, example files are needed for the NSM system components that creates exactly the same deployment that NSM integration test uses. It means the following two examples: basic and memory.

Are you seeing those as CR samples? Like the ones we have on our config/samples folder? We can talk about it on our meeting tomorrow.

Update: create CRs under samples. And possible one full CR that contains all options.


🚀 Feature: use GraphQL to discover gitlab group memberships

🔖 Feature description
When ingesting GitLab org data and determining the groups of which a GitLab user is a member, Instead of using the user memberships REST endpoint as is currently done:
https://github.com/backstage/backstage/blob/e9e5da25b832d2bbfaaadb2e73ec2ea6a8e1edb9/plugins/catalog-backend-module-gitlab/src/providers/GitlabOrgDiscoveryEntityProvider.ts#L219
let's determine group memberships using the GraphQL API -- ideally via the Group.groupMembers connection, which allows querying for direct membership specifically (rather than memberships inherited from parent groups as in the case of the UserCore.groupMemberships field).
🎤 Context
I'd like to be able to use the new GitLab org data integration with a very large GitLab instance (where making one API call per user might be impractical), and without an admin token.
✌ Possible Implementation
I've played around with this query, which would require one (paginated across descendant groups and memberships per group) non-admin API call per top-level group (these can themselves be fetched from the list group REST endpoint with the top_level_only parameter):
fragment BackstageGroup on Group {
  id
  path
  name
  description
  parent {
    id
  }
  groupMembers(relations: DIRECT, first: 100, after: $member_cursor) {
    nodes {
      user {
        username
      }
    }
  }
}

fragment OrgData on Group {
  ...BackstageGroup
  descendantGroups(first: 100, after: $group_cursor) {
    nodes {
      ...BackstageGroup
    }
  }
}

query Group {
  group(fullPath: "{full path of top-level group}") {
    ...OrgData
  }
}

👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR! However, @dpfaffenbauer indicated that they might take on this scope and I don't want to duplicate effort.

@jamieklassen let's make it together.

I would be interested in this too. Let me know if I can help in any way @jamieklassen or @dpfaffenbauer. I am hanging around on the Discord

@jamieklassen @weyert I've looked into the GraphQL API yesterday. I think we need to use both APIs, REST and GraphQL, right? The GraphQL Api only gives us sub-groups per groups and doesn't allow a full listing of groups

@dpfaffenbauer That's a good question. I always thought both APIs were in parity for these things. But I don't have an Admin PAT of the Gitlab instance I am using. So that's a bit difficult to answer for me 😅
For me it does appear to give the whole structure that I can see as a non-Admin user, though.

@weyert https://docs.gitlab.com/ee/api/graphql/reference/#querygroup needs a path, and the path cannot be empty.

Ah right, it was working when defining passing my group on Gitlab.com. Can imagine it is a problem when you have a self-hosted Gitlab instance 🤔

yep, that's what I meant when I said

these (the groups) can themselves be fetched from the list group REST endpoint with the top_level_only parameter

What do you think is the best approach? I am happy to only get the structure for a specific group that is against my permissions in the Gitlab instance.
Maybe we could consider to implement the GraphQL approach behind a feature flag?

I think the "specific group" thing is a separate enhancement, described in #16025 -- in my mind, this issue is about refactoring the parts of the integration that rely on the admin-only user memberships REST endpoint to use something from the GraphQL API instead.


ci: Add merge conflict labeler workflow

This adds a GitHub Action workflow that runs mschilde/auto-label-merge-conflicts once a day. As this repo (.github) is a special repository this will result on the action to be run on all Northstar repositories.
I expect at least some of our current ones to not have the merge conflict label and as such the workflow failing on those repo but that can be remedied by adding the label if we notice a workflow failing somewhere.

Welp apparently the internet lied to me cause this didn't work :c


Update dates.md

| 14. Dec. 2017  |Benkner    |What is Net Neutrality and why is it so heavily discussed?

Hi! Unfortunately this date is already taken by Mr. Arbeithuber. Could you please select a different date and send a new pull request? Greetings, Rainer Stropek.


VIEWS_FOLDER is now unused :fire: :scissors:

As of fbae08dd1c887bc5255f968c707bd2cd4e1cc36a, the constant is unused.
On top of that, removing it causes us not to autoload
manageiq-ui-classic gem!  :clap:
@martinpovolny :clap: 🙇

@Fryguy remember how I mentioned the views folder?  We still need the view info but at least it's not at class require time but at method call time.  👍

I should have removed it!

It's all good @martinpovolny.  I get a deletion out of it.  😆


Printing stops Javascript execution

Hi there,
I am currently looking for a possibility to display (and print) a pdf document within a webpage.  When I open the demo page (see link below) and click print, it seems Javascript execution is stopped at all for the whole page. I have verified this by setting up an simple interval using the console.
setInterval(() => console.log(new Date()), 500);
https://mozilla.github.io/pdf.js/web/viewer.html
I have experienced the same issue when printing the content of any div by script, regardless which async way I have tried.
Is this a know issue, or is thera a way how to circumvent this issue?
Or is this behaviour by design?
Thanks a lot,
Dietmar

I can reproduce this on any web-page (e.g. even http://example.com/) in both Firefox and Chrome, by manually triggering printing with window.print() (which is what the demo viewer uses), hence this is a more general browser issue and not a PDF.js library one as far as I can tell.
Looking at https://developer.mozilla.org/en-US/docs/Web/API/Window/print, there's also this sentence which seem to explain things:

In most browsers, this method will block while the print dialog is open. However in more recent versions of Safari, it may return immediately.

All-in-all, closing as "invalid" here since this is a browser (or possibly even specification) limitation and not actually related to and/or caused by the PDF.js demo viewer.


agent: import letsencrypt X3 cross signed certificate to ssvm agent keystore

This imports letsencypt X3 cross signed certificate to the default
keystore file for ssvm agent.
This fixes #2541.
Example listing:
$ keytool -list -keystore realhostip.keystore
Keystore type: JKS
Keystore provider: SUN

Your keystore contains 5 entries

root, Feb 3, 2012, trustedCertEntry,
Certificate fingerprint (SHA1): 27:96:BA:E6:3F:18:01:E2:77:26:1B:A0:D7:77:70:02:8F:20:EE:E4
realhostip, Feb 3, 2012, PrivateKeyEntry,
Certificate fingerprint (SHA1): DD:DB:44:55:E8:CF:33:4D:CB:54:B1:5A:95:A3:60:38:C3:1B:EF:7D
letsencryptauthorityx3cross, Apr 7, 2018, trustedCertEntry,
Certificate fingerprint (SHA1): E6:A3:B4:5B:06:2D:50:9B:33:82:28:2D:19:6E:FE:97:D5:95:6C:CB
cross, Feb 3, 2012, trustedCertEntry,
Certificate fingerprint (SHA1): DE:70:F4:E2:11:6F:7F:DC:E7:5F:9D:13:01:2B:7E:68:7A:3B:2C:62
intermed, Feb 3, 2012, trustedCertEntry,
Certificate fingerprint (SHA1): 7C:46:56:C3:06:1F:7F:4C:0D:67:B3:19:A8:55:F6:0E:BC:11:FC:44

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Screenshots (if appropriate):
How Has This Been Tested?

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
Testing
[ ] I have added tests to cover my changes.
[ ] All relevant new and existing integration tests have passed.
 I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1886

@rhtyd thanks for updating the CA certificates into CloudStack's one. Out of curiosity, do you have an idea if it would be too complicated to change the name of this CA keystore? Something like cloudstack.keystore looks better, than realhost.keystore.

Yes, you're right @rafaelweingartner it's not difficult to rename the keystore at all. In fact, I'm even considering, to get rid of this keystore file or symlink to the default system one (at /etc/ssl/certs/java/cacert, with password: changeit). The issue I found was that even when I updated the system cacert the agent failed to load that, since the old keystore file is used by default. Doing so may require some testing around using custom SSL certs for both SSVM and CPVM. Keeping a separate ca-cert file for cloudstack will cause a pain, when another provider's cert/chain are missing.

I think it is ok to customize the default cacerts with users certificates. However, I am not sure if we already have an execution flow that could achieve this. The good point on using the default cacerts is that on every update of the OS (of the system VM template) we get the updates in cacerts "automatically".

Let me re-visit the approach this or next week, we have an interim solution that works if anyone wants to use.

I've moved fix to https://github.com/apache/cloudstack/pull/2616

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1984


ICFolder uses name

ICFolder overwrites the object getter name. name is supposed to be accountName which was an issue in endpoint before as well.
A change of that getter might change the UI, as the toolbuilder was told (at least for the endpoint part) to use the object name, and not a more fitting variable like accountName
This requires changes in Core and UI as well

This was fixed by #262


show quorum in propmon ui

tracks "active" (voting) stage for governor proposals; gets quorum only once active