# connection slot, plus lock space (see max_locks_per_transaction). # Note: Increasing max_connections costs ~400 bytes of shared memory per Max_connections = 100 # (change requires restart) # Note: In RHEL/Fedora installations, you can't set the port number here #listen_addresses = 'localhost' # what IP address(es) to listen on #external_pid_file = '(none)' # write an extra PID file # If external_pid_file is not explicitly set, no extra PID file is written. #ident_file = 'ConfigDir/pg_nf' # ident configuration file #hba_file = 'ConfigDir/pg_hba.conf' # host-based authentication file #data_directory = 'ConfigDir' # use data in another directory # option or PGDATA environment variable, represented here as ConfigDir. # The default values of these variables are driven from the -D command-line # Memory units: kB = kilobytes Time units: ms = milliseconds Some parameters can be changed at run time # Any parameter can also be given as a command-line option to the server, e.g., # parameters, which are marked below, require a server shutdown and restart to # server for the changes to take effect, or use "pg_ctl reload". If you edit the file on a running system, you have to SIGHUP the # This file is read on server startup and when the server receives a SIGHUP # Re-commenting a setting is NOT sufficient to revert it to the default value # The commented-out settings shown in this file represent the default values. # values can be found in the PostgreSQL documentation. The complete list of parameter names and allowed # (The "=" is optional.) Whitespace may be used. # This file consists of lines of the form: The location of nf will be different depending on what operating system you are using. It has permission 600 which explains why you have a hard time finding it with a file search. Notice it is owned by postgres: -rw- 1 postgres postgres 19332 Oct 14 09:38 Here is where mine is on Fedora 17: /]# ll /var/lib/pgsql/data/nf The reason you may have trouble finding nf is because it is owned by postgres, not root. The total outage reportedly lasted 1h 5m, with the company later stating that it was caused by human error, when an erroneous change was made to the configuration of an internal tool.Query the database with the sql query: SHOW config_file We appreciate your patience during our investigation of this outage. Users may need to reload their apps to see this restoration. Slack is now back up and all features are functional. For those still experiencing problems, Slack advises reloading apps. Not too long afterward, the company said it had resolved the issue. We appreciate your patience in the meantime. We’re investigating and will let you know as soon as we know more. Users may be experiencing trouble with sending messages, using workflows and various other actions in Slack. Slack experiencing an outage across the app. This was later upgraded to a service outage. Users may be experiencing trouble with sending messages in Slack. Slack later posted a status update acknowledging issues. Widespread reports of a Slack outage this morning were acknowledged by the company, which escalated its investigation from an initial report of “trouble sending messages” to a full-scale “outage” … Slack outageĭowndetector showed a big spike in reports starting at around 5 a.m.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |