[MDEV-13810] Wrong systemd section name in comment within mariadb.service Created: 2017-09-15  Updated: 2020-08-25  Resolved: 2017-09-15

Status: Closed
Project: MariaDB Server
Component/s: Scripts & Clients
Affects Version/s: 10.2.8
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Hartmut Holzgraefe Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Linux with systemd

Issue Links:
Duplicate
duplicates MDEV-13809 Wrong systemd section name in comment... Closed

 Description   

The following comment in mariadb.service says that the [service] section should be used to add values to the MYSQLD_OPTS environment variable. This doesn't work though, it has to be [Service] with an upper case 'S'

# Start main service
 
# MYSQLD_OPTS here is for users to set in /etc/systemd/system/mariadb.service.d/MY_SPECIAL.conf
 
# Use the [service] section and Environment="MYSQLD_OPTS=...".
 
# This isn't a replacement for my.cnf.
 
# _WSREP_NEW_CLUSTER is for the exclusive use of the script galera_new_cluster
 
ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION



 Comments   
Comment by Hartmut Holzgraefe [ 2017-09-15 ]

Duplicate of MDEV-13809. I re-submitted after getting this error:

""Exception occurred: com.atlassian.jira.exception.DataAccessException: java.sql.SQLNonTransientConnectionException: Could not read resultset: unexpected end of stream, read 0 bytes from 4 Query is : set autocommit=0""

but apparently the error only happened after creating the issue, when trying to display results.

Generated at Thu Feb 08 08:08:33 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.