fred-users

fred-users@lists.nic.cz

405 discussions

RE: payments - invoices and statements on FRED registry system

by Dr P Nyirenda

Hello, I would like to find out how your registry responds to a request like the one here below for invoices and statements on registrar payments to a registry that uses the FRED registry system. On our registry for the Malawi .mw ccTLD, registrar payments are credited to the registrar zone by zone according to what the registrar has paid for. Once the registrar has consumed the credit, then they need to make a new payment in advance which is then credited to the zones that they need. We do not need to issue them an invoice in advance, they make the payments based on what transactions they need to do on each zone. When we receive a request for their data payments, we have used Invoice on Daphne to generate the data and we have sent this to the registrar. However, as you can see here below, this registrar seems to be asking for more. I would therefore like to request information on how your registry using FRED handles requests for data, invoices and statements like these. Regards, Paulos ====================== Dr Paulos B Nyirenda NIC.MW & .mw ccTLD http://www.registrar.mw ------- Forwarded message follows ------- From: Jamil Kamaly <Jamil.Kamaly(a)NetNames.com> To: "paulos(a)sdnp.org.mw" <paulos(a)sdnp.org.mw> Copies to: Michal Czyz <Michal.Czyz(a)NetNames.com>, domains mw <domains(a)registrar.mw>, PB Nyirenda <pb.nyirenda(a)gmail.com> Subject: RE: Malawi payments. Date sent: Wed, 14 Jun 2017 11:56:39 +0000 Hi Dr Paulos, I think you might have misunderstood, I wasn’t complaining. The details you provided me in April was excel spreadsheet with payment details and the zones that were topped. We need proper invoices and statements and therefore I was following up on our last conversation where you was saying that you are developing a system to make this possible. I was just checking if this is now possible and would we be getting proper statements and invoices. Thank you. Kind regards, Jamil ---------------------------------------------------------- Malawi SDNP Webmail: http://www.sdnp.org.mw Access your Malawi SDNP e-mail from anywhere in the world. ----------------------------------------------------------

7 let, 5 měsíců

Maximum renewal period in FRED

by Dr Paulos B Nyirenda

Jaromir, Just one or two more clarifications on FRED: 1. Is there a default maximum number of years (or months) for renewing a domain ? I see that in .cz this is required to be 10 years - is this burned into FRED or can it be modified? See: https://www.nic.cz/files/nic/doc/Registration_rules_CZ.pdf Regards, Paulos ====================== Dr Paulos B Nyirenda NIC.MW & .mw ccTLD http://www.registrar.mw

7 let, 8 měsíců

Invitation à participer à Meetup#2 Présentation et Workshop Openstack

by Ousmane Sanogo

Vous avez reçu une invitation ! -------------------------------------- Rejoignez Ousmane Sanogo à Meetup#2 Présentation et Workshop Openstack Quand : samedi 29 avril 2017, 09:00 Où : Ecole Agitel-Formation 132, Abidjan, Côte d'Ivoire, Abidjan Ce Meetup est organisé par Openstack Côte d'Ivoire. Après une première rencontre pour fêter les 6 ans de Openstack et le lancement du groupe d'utilisateur de Côte d'ivoire, nous organisons un second Meetup qui va vous permettre de mieux connaitre Open... https://secure.meetup.com/n/?s=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkZXN… -------------------------------------- ------- Message envoyé par Meetup de la part de Ousmane Sanogo (https://www.meetup.com/fr-FR/Openstack-Cote-divoire/members/212092234/) depuis Openstack Côte d'Ivoire. Une question? Vous pouvez contacter le support Meetup via support(a)meetup.com Je ne souhaite plus recevoir ce type d'e-mail (https://secure.meetup.com/n/?s=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJob29…) Meetup Inc. (https://www.meetup.com/fr-FR/), POB 4668 #37895 New York NY USA 10163

7 let, 8 měsíců

new documentation for FRED (available on github)

by Jaromir Talir

Hi, in addition to new FRED release, we have also released a new website at https://fred.nic.cz and completely new documentation system. Documentation url is https://fred.nic.cz/documentation. I feel importance of this deserves to use separate email for announcement. New documentation is searchable and it contains many new graphical schemas important to understand FRED architecture and processes. Source code of this documentation in reStructuredText format is available on github https://github.com/CZ-NIC/fred-docs. This means that you are more then welcomed to submit comments or preferably pull requests for things that you think they are missing in documentation. Please, check documentation and let us know what you think about this. Regards, Jaromir

7 let, 8 měsíců

new version FRED-2.29

by Jaromir Talir

Hi, we have published FRED version 2.29. During several previous releases we have rewritten almost all code responsible for EPP communication with registrars. This refactoring was necessery for implementation of new features in the future. Here is a compilation of some significant changes. - support for more operating systems. For the first time we provide also packages for latest RHEL/Centos version 7. Since Ubuntu 12.04 will lost its long term support in April, we will not provide packages for this version anymore. Preffered version of Ubuntu is 16.04. We use Ubuntu 16.04 in production for some time without any issues. This also means that Ubuntu 16.04 is most tested platform. In other platforms we only run limited set of automated tests so registries are required to do more indepth tests themselves. - configurable domain name format checking. Checking of validity of domain name is configurable per zone via linking to set of preconfigured checkers in database table zone_domain_name_validation_checker_map. - new idn support configuration. There used to be allow_idn option in server configuration file that meant that regular registrars are able to register domains in xn-- format (idn domains) in all zones. In current version it is possible to configure idn support per zone via mechanism mentioned earlier. Support for idn is just another preconfigured checker. - configurable dnssec algorithm checking. Until now, there was no checking of dnssec algorithm number used in EPP create_keyset or update_keyset EPP commands. If registries would like to limit this check only for some algorithms, they can do that via modification of database tables dnssec_algorithm and dnssec_algorithm_blacklist. - configurable limit of minimal number of nameservers in nsset. Until now, there was hardcoded requirement to have at least 2 nameservers and maximum 10 nameservers in nsset. Since this was limitation for some registries that wanted to use FRED, we moved this limit into configuration option nsset_min_hosts and nsset_max_hosts in server configuration file - asynchronous notification about EPP events. Notifications for domain state change has always been generated asynchronously via fred-admin commands, but notifications about EPP events done by registrars were created as part of EPP operation. To speed up system a little bit and to be able to continue EPP operation even when notification system is down, we made also notification about EPP events asynchronnous. So don't forget to add into cron system command 'fred-admin -- notify_email_objects_events' in intervals of your preference if you want to keep sending notifications. Regards, Jaromir

7 let, 8 měsíců

FRED and Apache 2.4 on Ubuntu 14.04

by Mario Guerra

People: A nagging problem we had when we migrated FRED to Ubuntu 14.04 (until a couple of weeks ago we ran 2.22 on Ubuntu 12.04) was that, suddenly, Apache connections gave us a CLOSE_WAIT, not a clean closing of the connection. This gave us a real headache with both our whois server and our EPP server. The solution?. Well, simply uninstall the mpm_event Apache module and install the mem_prefork one: a2dismod mpm_event a2enmod mem_prefork service apache2 restart I hope this helps the people using FRED under Ubuntu 14.04 experiencing a similar problem. ------------ Mario Guerra NIC-CR

7 let, 10 měsíců

ERROR HEADER: unpack requires a string argument of length 4

by Jakub Andrys

Hi, I have clean install of Ubuntu 16.04 server and I use script install: https://fred.nic.cz/page/2906/installation-on-ubuntu/ everything looks OK, but when I wan use fred-client, got this error: # fred-client FredClient upstream/2.7.0-97-g21a67 Type "help", "license" or "credits" for more information. Using configuration from /root/.fred-client.conf Used socket type: IPv6. Socket timeout: 10.0 sec. Connecting to localhost, port 700 ... Connection established. Try to open SSL layer... SSL layer opened. ERROR: ERROR HEADER: unpack requires a string argument of length 4 Server didn't return Greeting message. Contact server administrator. in /var/log/fred-eppd.log [19/Jan/2017:10:02:56 +0100] ::1 (process:2354) [sessionID 352216] Could not obtain object reference for alias 'EPP_alias'. Check mod_corba's configuration. [19/Jan/2017:10:02:56 +0100] ::1 (process:2354) [sessionID 352216] Could not obtain object reference for alias 'EPP_alias'. Connection on port 700 looks OK. Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 192.168.120.153:53 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN tcp6 0 0 :::43 :::* LISTEN tcp6 0 0 :::80 :::* LISTEN tcp6 0 0 :::53 :::* LISTEN tcp6 0 0 :::22 :::* LISTEN tcp6 0 0 :::25 :::* LISTEN tcp6 0 0 :::2809 :::* LISTEN tcp6 0 0 ::1:953 :::* LISTEN tcp6 0 0 :::443 :::* LISTEN tcp6 0 0 :::700 :::* LISTEN udp 0 0 192.168.120.153:53 0.0.0.0:* udp 0 0 127.0.0.1:53 0.0.0.0:* udp 0 0 0.0.0.0:68 0.0.0.0:* udp6 0 0 :::53 :::* Any idea whats wrong? Regards, Jakub

7 let, 11 měsíců

Weak digest algorithm @ archive.nic.cz

by Torkil Zachariassen

While running # apt-get update on Ubunto-16 as warning is issued: W: http://archive.nic.cz/ubuntu/dists/xenial/Release.gpg: Signature by key 55360425D50EB41DB9A21E67F20C079E020ADBB4 uses weak digest algorithm (SHA1) It seems that Debian and friends do not like SHA1 any longer. They provide more info on the removal of sha1 and how to fix a half-broken repositories https://wiki.debian.org/Teams/Apt/Sha1Removal I suppose the fred repository for ubunto at archive.nic.cz could be updated along those lines.

7 let, 11 měsíců

IDN in fred? Howto

by Torkil Zachariassen

We are to try out having a few extra national characters áýúíóæøåð and in uppercase these are ÁÝÚÍÓÆØÅÐ in ccTLD names (.fo) We found the 'allow_idn' in server.conf and have it set as 'true' (allow_idn = true), but this seems not to be enough, and does not really fullfill the requirements. IDN is mentioned an option in fred, but where/how can we turn this on, and what should we be aware of ? ...torkil...

7 let, 11 měsíců

On Ubuntu 16.04.1 LTS - updating broke fred

by Torkil Zachariassen

Sorry for this lengthy message, but a bugfix is provided with a description of the issue in the latest packages of fred for ubunto Have a nice day On Ubuntu 16.04.1 LTS - just updated and upgraded everything including fred, broke fred # systemctl status fred-logd ● fred-logd.service - FRED logging daemon Loaded: loaded (/lib/systemd/system/fred-logd.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Fri 2016-12-30 16:56:12 WET; 17min ago Process: 3653 ExecStart=/usr/sbin/fred-logd -ORBendPoint giop:tcp::2226 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-logd.conf (code=exited, status=1/FAILURE) Main PID: 3653 (code=exited, status=1/FAILURE) Dec 30 16:56:12 fred-ubunto-16 systemd[1]: fred-logd.service: Failed with result 'exit-code'. Dec 30 16:56:12 fred-ubunto-16 systemd[1]: fred-logd.service: Service hold-off time over, scheduling restart. Dec 30 16:56:12 fred-ubunto-16 systemd[1]: Stopped FRED logging daemon. Dec 30 16:56:12 fred-ubunto-16 systemd[1]: fred-logd.service: Start request repeated too quickly. Dec 30 16:56:12 fred-ubunto-16 systemd[1]: Failed to start FRED logging daemon. Hmm where is fred-logd.conf ? In /etc/init/fred-logd.conf ! BUGFIX # cd /etc/fred # ln -s ../init/fred-logd.conf root@fred-ubunto-16:/etc/fred# systemctl start fred-logd root@fred-ubunto-16:/etc/fred# systemctl status fred-logd ● fred-logd.service - FRED logging daemon Loaded: loaded (/lib/systemd/system/fred-logd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2016-12-30 17:22:57 WET; 2s ago Main PID: 4600 (fred-logd) Tasks: 3 Memory: 2.5M CPU: 25ms CGroup: /system.slice/fred-logd.service └─4600 /usr/sbin/fred-logd -ORBendPoint giop:tcp::2226 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-logd.conf Dec 30 17:22:57 fred-ubunto-16 systemd[1]: Started FRED logging daemon. So the bugfix worked :-) Next issue: # systemctl status fred-rifd ● fred-rifd.service - FRED registrar interface daemon Loaded: loaded ( ; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Fri 2016-12-30 16:50:26 WET; 35min ago Process: 3321 ExecStart=/usr/sbin/fred-rifd -ORBendPoint giop:tcp::2224 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-rifd.conf (code=exited, status=1/FAILURE) Main PID: 3321 (code=exited, status=1/FAILURE) Dec 30 16:50:25 fred-ubunto-16 systemd[1]: fred-rifd.service: Main process exited, code=exited, status=1/FAILURE Dec 30 16:50:25 fred-ubunto-16 systemd[1]: fred-rifd.service: Unit entered failed state. Dec 30 16:50:25 fred-ubunto-16 systemd[1]: fred-rifd.service: Failed with result 'exit-code'. Dec 30 16:50:26 fred-ubunto-16 systemd[1]: fred-rifd.service: Service hold-off time over, scheduling restart. Dec 30 16:50:26 fred-ubunto-16 systemd[1]: Stopped FRED registrar interface daemon. Dec 30 16:50:26 fred-ubunto-16 systemd[1]: fred-rifd.service: Start request repeated too quickly. Dec 30 16:50:26 fred-ubunto-16 systemd[1]: Failed to start FRED registrar interface daemon. Again /lib/systemd/system/fred-rifd.service specifies fred-rifd.conf to be in /etc/fred, were as it is in /etc/init :-/ BUGFIX # cd /etc/fred # ln -s ../init/fred-rifd.conf # cd # systemctl start fred-rifd # systemctl status fred-rifd ● fred-rifd.service - FRED registrar interface daemon Loaded: loaded (/lib/systemd/system/fred-rifd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2016-12-30 17:30:01 WET; 6s ago Main PID: 4777 (fred-rifd) Tasks: 3 Memory: 3.3M CPU: 31ms CGroup: /system.slice/fred-rifd.service └─4777 /usr/sbin/fred-rifd -ORBendPoint giop:tcp::2224 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-rifd.conf Dec 30 17:30:01 fred-ubunto-16 systemd[1]: Started FRED registrar interface daemon. So the bugfix worked :-) Next issue: # systemctl status fred-pifd ● fred-pifd.service - FRED public interface daemon Loaded: loaded (/lib/systemd/system/fred-pifd.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Fri 2016-12-30 16:28:07 WET; 1h 7min ago Process: 1334 ExecStart=/usr/sbin/fred-pifd -ORBendPoint giop:tcp::2223 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-pifd.conf (code=exited, status=1/FAILURE) Main PID: 1334 (code=exited, status=1/FAILURE) Tasks: 0 Memory: 0B CPU: 0 CGroup: /system.slice/fred-pifd.service Dec 30 16:28:07 fred-ubunto-16 systemd[1]: fred-pifd.service: Main process exited, code=exited, status=1/FAILURE Dec 30 16:28:07 fred-ubunto-16 systemd[1]: fred-pifd.service: Unit entered failed state. Dec 30 16:28:07 fred-ubunto-16 systemd[1]: fred-pifd.service: Failed with result 'exit-code'. Dec 30 16:28:07 fred-ubunto-16 systemd[1]: fred-pifd.service: Service hold-off time over, scheduling restart. Dec 30 16:28:07 fred-ubunto-16 systemd[1]: Stopped FRED public interface daemon. Dec 30 16:28:07 fred-ubunto-16 systemd[1]: fred-pifd.service: Start request repeated too quickly. Dec 30 16:28:07 fred-ubunto-16 systemd[1]: Failed to start FRED public interface daemon. BUGFIX # cd /etc/fred # ln -s ../init/fred-pifd.conf # cd # systemctl start fred-pifd # systemctl status fred-pifd ● fred-pifd.service - FRED public interface daemon Loaded: loaded (/lib/systemd/system/fred-pifd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2016-12-30 17:36:47 WET; 10ms ago Main PID: 4941 (fred-pifd) Tasks: 1 Memory: 1.1M CPU: 5ms CGroup: /system.slice/fred-pifd.service └─4941 /usr/sbin/fred-pifd -ORBendPoint giop:tcp::2223 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-pifd.conf Dec 30 17:36:47 fred-ubunto-16 systemd[1]: Started FRED public interface daemon. So the bugfix worked :-) Next issue: # systemctl status fred-msgd ● fred-msgd.service - FRED messaging daemon Loaded: loaded (/lib/systemd/system/fred-msgd.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Fri 2016-12-30 16:28:06 WET; 1h 9min ago Process: 1258 ExecStart=/usr/sbin/fred-msgd -ORBendPoint giop:tcp::2228 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-msgd.conf (code=exited, status=1/FAILURE) Main PID: 1258 (code=exited, status=1/FAILURE) Dec 30 16:28:05 fred-ubunto-16 systemd[1]: fred-msgd.service: Unit entered failed state. Dec 30 16:28:05 fred-ubunto-16 systemd[1]: fred-msgd.service: Failed with result 'exit-code'. Dec 30 16:28:06 fred-ubunto-16 systemd[1]: fred-msgd.service: Service hold-off time over, scheduling restart. Dec 30 16:28:06 fred-ubunto-16 systemd[1]: Stopped FRED messaging daemon. Dec 30 16:28:06 fred-ubunto-16 systemd[1]: fred-msgd.service: Start request repeated too quickly. Dec 30 16:28:06 fred-ubunto-16 systemd[1]: Failed to start FRED messaging daemon. Same thing BUGFIX # cd /etc/init # ln -s ../init/fred-msgd.conf # cd # systemctl start fred-msgd # systemctl status fred-msgd ● fred-msgd.service - FRED messaging daemon Loaded: loaded (/lib/systemd/system/fred-msgd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2016-12-30 17:38:59 WET; 4s ago Main PID: 5016 (fred-msgd) Tasks: 3 Memory: 1.6M CPU: 20ms CGroup: /system.slice/fred-msgd.service └─5016 /usr/sbin/fred-msgd -ORBendPoint giop:tcp::2228 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-msgd.conf Dec 30 17:38:59 fred-ubunto-16 systemd[1]: Started FRED messaging daemon. So the bugfix worked :-) Next issue: # systemctl status fred-adifd ● fred-adifd.service - FRED administration interface daemon Loaded: loaded (/lib/systemd/system/fred-adifd.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Fri 2016-12-30 16:28:08 WET; 1h 12min ago Process: 1352 ExecStart=/usr/sbin/fred-adifd -ORBendPoint giop:tcp::2222 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-adifd.conf (code=exited, status=1/FAILURE) Main PID: 1352 (code=exited, status=1/FAILURE) Dec 30 16:28:07 fred-ubunto-16 systemd[1]: fred-adifd.service: Unit entered failed state. Dec 30 16:28:07 fred-ubunto-16 systemd[1]: fred-adifd.service: Failed with result 'exit-code'. Dec 30 16:28:08 fred-ubunto-16 systemd[1]: fred-adifd.service: Service hold-off time over, scheduling restart. Dec 30 16:28:08 fred-ubunto-16 systemd[1]: Stopped FRED administration interface daemon. Dec 30 16:28:08 fred-ubunto-16 systemd[1]: fred-adifd.service: Start request repeated too quickly. Dec 30 16:28:08 fred-ubunto-16 systemd[1]: Failed to start FRED administration interface daemon. Again same thing BUGFIX # cd /etc/fred # ln -s ../init/fred-adifd.conf # cd # root@fred-ubunto-16:~# systemctl start fred-adifd # root@fred-ubunto-16:~# systemctl status fred-adifd ● fred-adifd.service - FRED administration interface daemon Loaded: loaded (/lib/systemd/system/fred-adifd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2016-12-30 17:41:42 WET; 4s ago Main PID: 5128 (fred-adifd) Tasks: 4 Memory: 3.3M CPU: 29ms CGroup: /system.slice/fred-adifd.service └─5128 /usr/sbin/fred-adifd -ORBendPoint giop:tcp::2222 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-adifd.conf Dec 30 17:41:42 fred-ubunto-16 systemd[1]: Started FRED administration interface daemon. Final check # fred-status && echo ok ok DONE :-) NOTE fred-status is a local script which looks like this: ####################################################################### #!/bin/sh # File: fred-status.sh # Purpose: Check that fred runs all the 7 required processes # Author: Torkil Zachariassen # Date: 20161209 CMD="ps -u fred --no-headers" count=`$CMD|wc -l` if [ $count -ne 7 ]; then echo ERROR Wrong number of processes $CMD exit 1 fi # return ok return 0 NOTE $ ps -u fred should return the following processes PID TTY TIME CMD 1096 ? 00:01:32 fred-webadmin 1181 ? 00:00:03 fred-logd 1182 ? 00:00:00 fred-rifd 1217 ? 00:00:00 fred-pifd 1218 ? 00:00:01 fred-adifd 3574 ? 00:00:00 fred-msgd 3685 ? 00:00:05 fred-pyfred ####################################################################### It seems that the problem are the following lines in fred-* in /lib/systemd/system: # grep /fred/fred /lib/systemd/system/fred-* /lib/systemd/system/fred-adifd.service:ExecStart=/usr/sbin/fred-adifd -ORBendPoint giop:tcp::2222 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-adifd.conf /lib/systemd/system/fred-logd.service:ExecStart=/usr/sbin/fred-logd -ORBendPoint giop:tcp::2226 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-logd.conf /lib/systemd/system/fred-msgd.service:ExecStart=/usr/sbin/fred-msgd -ORBendPoint giop:tcp::2228 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-msgd.conf /lib/systemd/system/fred-pifd.service:ExecStart=/usr/sbin/fred-pifd -ORBendPoint giop:tcp::2223 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-pifd.conf /lib/systemd/system/fred-rifd.service:ExecStart=/usr/sbin/fred-rifd -ORBendPoint giop:tcp::2224 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-rifd.conf as these references configuration files in /etc/fred, whereas the actual configuration files are installed in /etc/init As I am unsure of what the correct solution might be I will leave this issue to the packager Have a nice day :-)

7 let, 11 měsíců

← Newer
1
...
8
9
10
11
12
13
14
...
41
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

fred-users