Hi Alex,
seems to work, here is the output of the command ' fdbcli —exec status ':
[centos@localhost foundationdb]$ fdbcli --exec status
Using cluster file `/etc/foundationdb/fdb.cluster'.
Configuration:
Redundancy mode - single
Storage engine - memory-2
Coordinators - 1
Cluster:
FoundationDB processes - 1
Zones - 1
Machines - 1
Memory availability - 1.9 GB per process on machine with least
available
>>>>> (WARNING: 4.0 GB recommended) <<<<<
Fault Tolerance - 0 machines
Server time - 02/20/20 12:08:10
Data:
Replication health - Healthy
Moving data - 0.000 GB
Sum of key-value sizes - 0 MB
Disk space used - 105 MB
Operating space:
Storage server - 1.0 GB free on most full server
Log server - 10.6 GB free on most full server
Workload:
Read rate - 7 Hz
Write rate - 0 Hz
Transactions started - 3 Hz
Transactions committed - 0 Hz
Conflict rate - 0 Hz
Backup and DR:
Running backups - 0
Running DRs - 0
Client time: 02/20/20 12:08:10
One additional info:
The first run of
sudo rpm -i --force --nodeps ./foundationdb-server-6.2.15-1.el7.x86_64.rpm
gives me some errors (german locale) and i don't know why:
tr: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
tr: Schreibfehler
tr: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
tr: Schreibfehler
I tried the command again, which gives me no errors...
Ronny
Florian Beckert & Ronny Berndt GbR
Saalstr. 3
07743 Jena
Tel. 03641 - 6391110
Fax. 03641 - 219637
E-Mail: p...@kioskkinder.com
Am Do., 20. Feb. 2020 um 11:43 Uhr schrieb Will Holley <willhol...@gmail.com
>:
> For running in a container, you could also try using the Red Hat UBI
> instead of CentOS. There is a ubi-init variant which runs systemd (see
>
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/building_running_and_managing_containers/index#using_init_red_hat_base_images
> and
> https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image
> ).
>
> On Thu, 20 Feb 2020 at 10:30, Ronny Berndt <ro...@kioskkinder.com> wrote:
>
> > @Alex
> >
> > I have a running centos8 vm. Maybe i can help…
> >
> >
> > > Am 20.02.2020 um 11:13 schrieb Alex Miller
> <alexmil...@apple.com.INVALID
> > >:
> > >
> > >
> > >> On Feb 19, 2020, at 20:09, Joan Touzet <woh...@apache.org> wrote:
> > >> On 2020-02-19 23:00, Alex Miller wrote:
> > >>>> On Feb 19, 2020, at 16:07, Paul Davis <paul.joseph.da...@gmail.com>
> > wrote:
> > >>>>
> > >>>> foundationdb does take a while to build though, so finding binaries
> > >>>> might short circuit everything to be even a single apt-get line or
> > >>>> w/e.
> > >>> The build is both slow and quite memory hungry.
> > >>> In addition to FROM + COPY in docker, foundationdb.org hosts
> > downloads in both a tarball-of-binaries form and a .deb of the server.
> > >>>> Though that papers over CentOS support and the like. Dunno what that
> > >>>> story is like.
> > >>> RPMs for RHEL6 and RHEL7 are also published (which I think should
> > correlate to centos6 and centos7).
> > >>
> > >> Are there plans for a CentOS 8 RPM? CentOS 8 has been out since
> > September 2019, and is the only CentOS that we support with SpiderMonkey
> 60
> > today.
> > >
> > > I don't think anyone in FDB realized Centos 8 is out, so that's a good
> > question.
> > >
> > > After digging through packaging code, the only difference between the
> EL6
> > > and EL7 RPMs is that EL6 installs a sysv init script, and el7 installs
> a
> > systemd
> > > unit file. The binaries in both cases are built on centos6 and the
> > build system
> > > jumps through all the hoops of statically linking a C++ binary, so that
> > > fdbserver will run on anything centos6 or newer just fine. This should
> > > mean that EL7 RPMs are for EL7+, or at least, until Centos changes init
> > > systems again.
> > >
> > > But, that's just theory, and doing a quick install on a centos8 VM
> > sounded like
> > > it'd be qick and simple...
> > >
> > > Except parallels doesn't support centos8 out of the box yet, and I
> broke
> > a
> > > centos7 install trying to do an (unsupported) upgrade to centos8. So
> > that's
> > > out.
> > >
> > > Docker should save the day here, but it turns out that running systemd
> > in a
> > > docker container is nontrivial. Even when I did get systemd running as
> > PID 1,
> > > FoundationDB didn't start automatically for me, and systemctl doesn't
> > work,
> > > because centos:8 gives you a half baked systemd install that somehow
> > lacks dbus.
> > >
> > > So I'm out of easy options. fdbserver still runs manually just fine,
> > and all
> > > the files _look_ like they got installed in the right place. So if
> > someone has
> > > an actual running VM of Centos 8, it _seems_ like things should still
> > start fine
> > > when installing the EL7 RPM.
> > >
> > > This exercise did point out that centos8 intentionally doesn't provide
> a
> > /usr/bin/python,
> > > which FDB's RPM packages accidentally depend on, so I've posted
> > > https://github.com/apple/foundationdb/pull/2700 to get rid of that.
> One
> > > will have to use `rpm -i —force foundationdb-server*.rpm` until the
> > > next 6.2 release.
> >
> >
>
