is sigrok gone?

[brichards42]

It seems http://sigrok.org/ is down and has been for many days.

Is the project abandoned? Many searches turn up absolutely nothing about the site closing (or the fact it has been down a while).

[brichards42]

Why not check their github and file an issue there or something?

I believe the sigrok repos on gitub are mirror-only. The real repo is on sigrok.org (It also looks like you can't file an issue, only pull requests).

[Cerebus]

I went looking for it a few weeks back and it was not up.

Currently domain registration is OK. DNS lookup is OK. HTTP(S) connections to port 80 and port 443 fail with "connection refused" for both IPv4 and IPv6.

I believe that was the state of play when I went looking a few weeks back. I assumed at the time it was a temporary problem that someone would fix when they spotted it (I vaguely remember it being over the Xmas break). It seems that is not the case, but something more persistent.

[WattsThat]

Looks like server issues. The way back machine has several successful crawls through http://sigrok.org/ during January so it’s not always dead, just when you happen to check ;-)

[brichards42]

Looks like server issues. ... it’s not always dead, just when you happen to check ;-)

Ha, I just have really bad timing.

[brichards42]

If only they had some kind of hardware / software system to be able to easily capture and visualize for their system administrators
when something is 'up (1)' and something is 'down (0)'... then maybe they'd have an easier time detecting the problem...

Or maybe they do and the sample rate just accidentally got changed from 1ks/d to 1kd/s...

It's really hard these days to get set up for server monitoring... Or maybe they to monitor it but the same server also handles the email notifications.

[scopeman]

I went to the Wayback machine but it seems that they did not back up the installers for the programs.

Sam

[Nominal Animal]

Based on the sigrok-devel mailing list, I'd say it's just the web server at sigrok.org that is down, and nobody noticed or bothered to tell the list until Saturday (2022-02-05).  If the git interface (typically using SSH) and mailing lists work, it's easy for the devs to not notice the web server being down, since they don't actually use the web server for anything themselves.

It's not like you pay these guys to do their thing, after all.

[Cerebus]

Still on its back.

[abraxa]

Thanks for caring, the team is currently working on moving servers.

[brichards42]

Thanks for caring, the team is currently working on moving servers.

Appreciate the information, thanks.

[abraxa]

The page is back up, whatever is missing will follow in the coming days. Sorry for the downtime, sometimes things just happen at the worst time possible.

[JoeyG]

down again

[ebastler]

down again

Works fine from this side of the globe.

[SiliconWizard]

Fine here too. Maybe their occasional downtime every two years comes from them forgetting to renew the domain in time. Just a possibility. Then DNS takes a while to propagate back.

[PA0PBZ]

Fine here too. Maybe their occasional downtime every two years comes from them forgetting to renew the domain in time.

That's not it:

Created on 2009-03-20
Expires on 2025-03-20
Updated on 2024-01-25

Working fine from here too.

[ebastler]

We had a single person reporting an access problem. We don't know for how long the problem lasted since he has never reported back. I think we can let this matter rest.

[Nominal Animal]

I saw a host-unreachable error once yesterday, but couldn't reproduce/repeat it.  A possible (likely?) scenario is a temporary connection/routing issue that got cached by OP's browser, and they didn't force-reload the page, therefore getting a cached error page instead.

Whenever you get an error page, simply reloading the URL will not always do a full reload attempt.  For example, with Firefox, you need to do Shift+Ctrl+R (instead of just Ctrl+R) to bypass the cache and do a real full page reload.

(The underlying technical detail: when the error is displayed as a HTML page instead of simply passing a brute HTTP error to the client, the error HTML page is cacheable.  Those creating such pages should ensure the server includes Date: and Cache-Control: HTTP headers to explicitly disable caching such error pages (HTML <meta element http-equiv="Cache-Control" content="..." may not suffice for all browsers), but many proxies do not bother, leading to the kind of issues OP is seeing.)

[DaanWesterhof]

Hi, the sigrok website/servers seems to be down again. Im pretty sure it worked about 3 weeks ago so their certificate might be expired? I saw in an earlier post that it was till 20-3-2025 so that might be it. My browser currently just gives an error: connection timeout though. Tried on multiple laptops and networks to check if it had to do with me.

[SiliconWizard]

This now displays:

Code: [Select]

MediaWiki 1.37 internal error

Installing some PHP extensions is required.
I'm guessing they are updating the server, or maybe they just switched hosting services (which would correlate with the down time).

[amyk]

You can download it from archive.org too.

[bitwelder]

Well, also the sigrok gihub repository doesn't show much activity since several months already

[EEVblog]

This now displays:

Code: [Select]

MediaWiki 1.37 internal error

Installing some PHP extensions is required.
I'm guessing they are updating the server, or maybe they just switched hosting services (which would correlate with the down time).

Yep, same, it's borked.

[SiliconWizard]

Not sure what they are going to do.
The github repo shows some activity as PRs: https://github.com/sigrokproject/libsigrok
but no update to the repo itself for the last 6 months.
It's a read-only mirror repo too, so you can't open issues or anything other than PRs.

sigrok hosts (well, used to host) their own git repos, so that part is as unavailable now as the website.

It used to be a pretty active project. So I don't know what's up. Looks like the maintainer(s) stopped caring (maybe something bad happened, I don't know).

[bitwelder]

Second-most recent entry in the sigrok blog (from Oct 2024): not promising
https://www.sigrok.org/blog/current-project-status