Project

General

Profile

Bug #68871

S3 Service fails to start

Added by Waqar Ahmed 9 months ago. Updated 9 months ago.

Status:
Done
Priority:
No priority
Assignee:
Waqar Ahmed
Category:
Services
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

When I start the S3 service I receive an error message saying S3 service fails to start.


Related issues

Has duplicate FreeNAS - Bug #71085: s3 service failes to start Closed
Copied from FreeNAS - Bug #67602: Fix bug that prevented S3 service from startingDone

Associated revisions

Revision 07e35d3e (diff)
Added by Waqar Ahmed 9 months ago

S3 Service fails to start This commit introduces the following changes: 1) Fixes a bug where S3 service failed to start because S3 configuration was not generated in rc.conf.freenas when it was not set to start on boot. As the rc script for minio uses rc.conf.freenas for getting the values for starting S3 service, it failed. 2) There was a case where we could insert more then one row when config method for a config service were called simultaneously. This commit fixes that issue. 3) S3 was compromised by point no 2 as well in some scenarios. So this commit also fixes how we order the s3 rows if there are more then one to mirror it how middlewared does. Ticket: #68871

Revision 9523db3a (diff)
Added by Waqar Ahmed 9 months ago

S3 Service fails to start This commit introduces the following changes: 1) Fixes a bug where S3 service failed to start because S3 configuration was not generated in rc.conf.freenas when it was not set to start on boot. As the rc script for minio uses rc.conf.freenas for getting the values for starting S3 service, it failed. 2) There was a case where we could insert more then one row when config method for a config service were called simultaneously. This commit fixes that issue. 3) S3 was compromised by point no 2 as well in some scenarios. So this commit also fixes how we order the s3 rows if there are more then one to mirror it how middlewared does. Ticket: #68871

Revision 2d9f3f0b (diff)
Added by Waqar Ahmed 9 months ago

S3 Service fails to start This commit introduces the following changes: 1) Fixes a bug where S3 service failed to start because S3 configuration was not generated in rc.conf.freenas when it was not set to start on boot. As the rc script for minio uses rc.conf.freenas for getting the values for starting S3 service, it failed. 2) There was a case where we could insert more then one row when config method for a config service were called simultaneously. This commit fixes that issue. 3) S3 was compromised by point no 2 as well in some scenarios. So this commit also fixes how we order the s3 rows if there are more then one to mirror it how middlewared does. Ticket: #68871

Revision aa6f67e4 (diff)
Added by Waqar Ahmed 9 months ago

S3 Service fails to start This commit introduces the following changes: 1) Fixes a bug where S3 service failed to start because S3 configuration was not generated in rc.conf.freenas when it was not set to start on boot. As the rc script for minio uses rc.conf.freenas for getting the values for starting S3 service, it failed. 2) There was a case where we could insert more then one row when config method for a config service were called simultaneously. This commit fixes that issue. 3) S3 was compromised by point no 2 as well in some scenarios. So this commit also fixes how we order the s3 rows if there are more then one to mirror it how middlewared does. Ticket: #68871

History

#1 Updated by Waqar Ahmed 9 months ago

  • Copied from Bug #67602: Fix bug that prevented S3 service from starting added

#2 Updated by Waqar Ahmed 9 months ago

  • Status changed from In Progress to Ready for Testing

#3 Updated by Dru Lavigne 9 months ago

  • File deleted (debug-PNAS-20190104144044.tgz)

#4 Updated by Dru Lavigne 9 months ago

  • File deleted (minio.txt)

#5 Updated by Dru Lavigne 9 months ago

  • Status changed from Ready for Testing to Done
  • Target version changed from 11.3 to Master - FreeNAS Nightlies
  • Private changed from Yes to No
  • Needs QA changed from Yes to No
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#7 Updated by Waqar Ahmed 9 months ago

  • Has duplicate Bug #71085: s3 service failes to start added

Also available in: Atom PDF