Re: [Nix-dev] Monitoring by default
I like the idea too. It seems to me that distributions really lack metrics collection and data analysis. For example, it would be nice to have automatic gathering of the battery usage (charge/discharge/capacity) and an easy access to compiled historical data like the capacity loss over the years. I know this is far less ambitious than what you describe, but it would be a great entry point for new users. If they like it, they may want to gather wore statistics. Anyway, I think it makes total sense to have such a feature in NixOS. -- Layus. On 20/04/16 11:49, Rok Garbas wrote: > +1 for the initiative. i don't believe personally enabling monitoring > by default should be the right way to go (since we all use nixos in > different contexts), but having a commented instructions in generated > configurations.nix would be the way to go. > > it would be nice if systemd monitoring stuff could be used as well: > https://github.com/garbas/dotfiles/blob/master/nixos/rok.nix#L236 > above line makes systemd-cgtop showing numbers. > > > > On Wed, Apr 20, 2016 at 8:44 AM, Alexei Robyn wrote: >> Seems interesting. You mention alerts for "System software too old.", but >> the only vaguely-universal definition of "too old" I can think of would be >> "missing security updates", and that's both debatable and an area where >> NixOS is currently fairly lacking in infrastructure and tooling. >> >> Default collection of metrics beyond what is necessary to provide useful >> alerts is a bad idea. Alerts have essentially universal usefulness, >> statistics less so - they're unnecessary for most desktops and small >> servers. At least until you have issues, so of course it'd be nice if they >> were easy to switch on :p. >> >> - Alexei >> >> >> On Wed, Apr 20, 2016, at 12:40 AM, Svein Ove Aas wrote: >> >> Hi all, >> >> People who are not interested in reliability or monitoring can stop reading >> now. >> >> -- >> >> I've written up a "design doc" (statement of intent?) for how we might do >> monitoring-by-default. Once I think there is a reasonable level of consensus >> about how we should do this, I'll go ahead and implement what's in the >> document, but I'd like to make sure we're all on the same page first; >> especially as I want this to be on by default. >> >> So I'd like your input. Can you take a look? >> >> -- >> Svein Ove Aas >> ___ >> nix-dev mailing list >> nix-dev@lists.science.uu.nl >> http://lists.science.uu.nl/mailman/listinfo/nix-dev >> >> >> >> ___ >> nix-dev mailing list >> nix-dev@lists.science.uu.nl >> http://lists.science.uu.nl/mailman/listinfo/nix-dev >> > > ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Can a nixOps coordinator update itself?
I don't think it would be a problem but I wouldn't make promises. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Can a nixOps coordinator update itself?
Hi Nix-Ops devs, I'm currently using a separate online instance to deploy my nixos servers. This deploy instance is running nixos itself (I deployed it from a local vm with nixOps). Can the online instance update itself? Meaning it deploying updates via nixOps to itself? As I can always redeploy it from my local vm, I'm not really worried about system failure, as long as this doesn't affect the other deployed instances ofcourse ;-) Kind regards, Erik ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] break purity
Hi,
I've got a bunch of artifacts being built in the
/tmp/nix-build-component_name.drv-0
now I want to point the build manager, in this case cargo using the
CARGO_TARGET_DIR env var to put the artifacts into a directory I make
directly in the /tmp/target_${name}
This way any further compilations will reuse the artifacts and they
won't need to be rebuilt.
obviously nix doesn't allow me to do this.
Is there a dirty hack to allow creating and writing artifacts directly
to /tmp/target_${name}?
Why? We're using nix as a replacement for make, one major drawback is:
every time we change a line of code the entire component + trans deps
needs to be rebuilt. This takes a long time when transitive deps go
deep.
/sjm
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] break purity
You can set up a build environment resembling what nix-build would use
using the nix-shell command. All dependencies are provided, and each build
phase gets a function.
On 21 April 2016 at 17:42, stewart mackenzie wrote:
> Hi,
>
> I've got a bunch of artifacts being built in the
> /tmp/nix-build-component_name.drv-0
>
> now I want to point the build manager, in this case cargo using the
> CARGO_TARGET_DIR env var to put the artifacts into a directory I make
> directly in the /tmp/target_${name}
>
> This way any further compilations will reuse the artifacts and they
> won't need to be rebuilt.
>
> obviously nix doesn't allow me to do this.
>
> Is there a dirty hack to allow creating and writing artifacts directly
> to /tmp/target_${name}?
>
> Why? We're using nix as a replacement for make, one major drawback is:
> every time we change a line of code the entire component + trans deps
> needs to be rebuilt. This takes a long time when transitive deps go
> deep.
>
> /sjm
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Upgrade from 15.09 to 16.03 with NixOps
> The expressions are evaluated from the coordinator, so either you upgrade > the channel there or you check out nixpkgs somewhere and set > `NIX_PATH=nixpkgs=/path/to/your/clone` before running nixops. It is also possible to use `-I nixpkgs=` and point directly to the channel you want to use: nixops deploy -d DEPLOYMENT -I nixpkgs=https://github.com/NixOS/nixpkgs-channels/archive/nixos-16.03.tar.gz On Wed, Apr 20, 2016 at 09:42:37PM +, Wout Mertens wrote: > The expressions are evaluated from the coordinator, so either you upgrade > the channel there or you check out nixpkgs somewhere and set > `NIX_PATH=nixpkgs=/path/to/your/clone` before running nixops. > > On Wed, Apr 20, 2016 at 1:52 PM Teo Klestrup wrote: > > > I believe the channels are taken from the coordinator, so when the > > coordinator is upgraded then the other machines should be, too. > > On 18 Apr 2016 19:20, "4levels" <4lev...@gmail.com> wrote: > > > >> Hi Nix'ers, > >> > >> This is an Nix Ops related question. > >> > >> How can I specify which channel to use inside the nix expressions (*.nix > >> files) for nixops? > >> > >> Thanks in advance! > >> > >> Erik > >> > >> ___ > >> nix-dev mailing list > >> nix-dev@lists.science.uu.nl > >> http://lists.science.uu.nl/mailman/listinfo/nix-dev > >> > >> ___ > > nix-dev mailing list > > nix-dev@lists.science.uu.nl > > http://lists.science.uu.nl/mailman/listinfo/nix-dev > > > -- > > Wout. > (typed on mobile, excuse terseness) > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Eric Sagnes サニエ エリック ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] libxml2
Pushed in c4ab7e2cd4f5ad39a2f1d590af2d2b72037fdfb2. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] PolicyKit timeout after upgrade to 16.03
Hi Roger, I did find a workaround by disabling polkit alltogether. security.polkit.enable = false As soon as I re-enable polkit, the issue is back again. I will still file an issue for this, for now the systems work without polkit. As the servers are never running X, I'm still unsure if I need polkit at all. I do however use wkhtmltopdf which includes libX to be able to render PDF documents from an HTML output. Kind regards, Erik On Tue, Apr 19, 2016 at 8:27 AM Roger Qiu wrote: > You should try rolling back on the instance causing problems. By that I > mean rolling back on the system generation (at boot loader) not channel > generation. If it still has a problem, then something imperative occurred > and perhaps you can force rebuild the system (I forgot whether there's a > flag for this, or just deleting the some stuff would work)... also there's > some commands to check package integrity. You should always try to minimise > any imperative configuration (beyond disk and device setup as there's no > "nix-bootstrap") so things can be reproducible. > On 19/04/2016 12:19 AM, "4levels" <4lev...@gmail.com> wrote: > >> Hi Roger, >> >> the weird thing is that my local vm, the machine that actually deploys >> the servers, doesn't have this issue. This instance also runs nixos-16.03 >> and uses the same nixos-16.03-small channel. >> >> This issue started when trying to upgrade to 16.03 I was not really >> clear about how to do this so I ended up running nix-channel add ... nixos >> on all deployed servers, causing all the nixops deployed config to be lost, >> resulting in having to redeploy every server. Currently I'm still unsure >> how to upgrade machines deployed with nixops :-( >> >> I don't mind redeploying every machine to solve this, as the issues are >> piling up now: I need to reboot a server because I can't do any systemctl >> call anymore that requires root privileges. Even when first switching to >> the root account (I know the password), this issue persists. I'm still >> completely unsure where this issue comes from. Googling this error "Error >> getting authority: Error initializing authority: Error calling >> StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached >> (g-io-error-quark, 24)" gives me tons of pages with polkit, dbus and >> systemd things that go far beyond my understandings. >> >> When running the polkit service with strace, I can see loads of errors >> about files not being found and the trace ends with >> >> write(2, "Error switcing to user polkituse"..., 98Error switcing to user >> polkituser: Error changing to home directory /var/empty: Permission denied >> ) = 98 >> >> Please find attached the full strace log. I really hope someone can >> assist further in this nasty issue. Maybe it is related to the use of >> nixos-16.03-small instead of nixos-16.03. But since I'm using nixos for >> servers only, without the need for a desktop environment, I was expecting >> the small channel to be better.. >> >> Kind regards! >> >> Erik >> >> On Wed, Apr 13, 2016 at 12:57 PM Roger Qiu wrote: >> >>> Have you tried rolling back to 15.09, does it still happen? >>> >>> >>> On 13/04/2016 4:47 PM, 4levels wrote: >>> >>> Hi Nix'ers, >>> >>> No one? Im I the only one who's experiencing this? >>> >>> This timeout still occurs and makes every call to systemctl at least 30 >>> seconds slower, pretty annoying actually.. >>> >>> Hope someone with understanding can shed some light on what might be >>> going on here. >>> >>> Erik >>> >>> On Tue, Apr 12, 2016 at 3:00 AM 4levels < <4lev...@gmail.com> >>> 4lev...@gmail.com> wrote: >>> Hi Nix'ers, After upgrading to version 16.03 I'm facing timeouts whenever I try to restart a service via systemctl restart. I might be overlooking something obvious here, as I just ran nix-channel-add https://nixos.org/channels/nixos-16.03-small nixos nixos-rebuild boot --upgrade Any hints in what could be the issue? This is the full error message on the console: Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) I can run other commands through sudo though. Thanks! Erik >>> >>> ___ >>> nix-dev mailing >>> listnix-...@lists.science.uu.nlhttp://lists.science.uu.nl/mailman/listinfo/nix-dev >>> >>> >>> -- >>> Founder of Matrix AIhttps://matrix.ai/+61420925975 >>> >>> ___ >>> nix-dev mailing list >>> nix-dev@lists.science.uu.nl >>> http://lists.science.uu.nl/mailman/listinfo/nix-dev >>> >> ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Upgrade from 15.09 to 16.03 with NixOps
Hi Teo, Kevin and Wout, thank you all for your kind support. I do add the nixpkgs line and things seem to work correctly. I was just getting confused as this change initially didn't trigger a rebuild of the deployed system. Kind regards, Erik On Wed, Apr 20, 2016 at 11:42 PM Wout Mertens wrote: > The expressions are evaluated from the coordinator, so either you upgrade > the channel there or you check out nixpkgs somewhere and set > `NIX_PATH=nixpkgs=/path/to/your/clone` before running nixops. > > On Wed, Apr 20, 2016 at 1:52 PM Teo Klestrup wrote: > >> I believe the channels are taken from the coordinator, so when the >> coordinator is upgraded then the other machines should be, too. >> On 18 Apr 2016 19:20, "4levels" <4lev...@gmail.com> wrote: >> >>> Hi Nix'ers, >>> >>> This is an Nix Ops related question. >>> >>> How can I specify which channel to use inside the nix expressions (*.nix >>> files) for nixops? >>> >>> Thanks in advance! >>> >>> Erik >>> >>> ___ >>> nix-dev mailing list >>> nix-dev@lists.science.uu.nl >>> http://lists.science.uu.nl/mailman/listinfo/nix-dev >>> >>> ___ >> nix-dev mailing list >> nix-dev@lists.science.uu.nl >> http://lists.science.uu.nl/mailman/listinfo/nix-dev >> > -- > > Wout. > (typed on mobile, excuse terseness) > ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
