97
Veteran Member
RIP Telnet
Posts: 889
| Likes: 679
|
Post by 97 on May 26, 2020 22:57:50 GMT
After Seth restarted the server, every non senior got their ranks reset. Either we have to manually re-add everyone or a fix is going to have to be made.
Apparently the seniors can only admins to a super, but not a telnet.
|
|
JagWire
Veteran Member
Woof
Posts: 3,734
| Likes: 2,143
|
Post by JagWire on May 26, 2020 23:00:08 GMT
Is there not a backup of the superadmin list?
|
|
|
|
Post by Polaris Seltzeris on May 26, 2020 23:06:36 GMT
Woohoo for quality assurance... woohoo for backups... woohoo for not using a database... woohoo for deployment...
|
|
decyj145
Veteran Member
Indefinitely inactive.
Posts: 1,877
| Likes: 774
|
Saconfig
May 26, 2020 23:06:57 GMT
via mobile
Post by decyj145 on May 26, 2020 23:06:57 GMT
Well apparently seniors can set ranks but have to be case sensitive when they’re typing the command or something?
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 26, 2020 23:12:53 GMT
im literally looking at the database and everyones ranks are fine.
|
|
|
|
Post by DragonSlayer2189 on May 26, 2020 23:41:51 GMT
Woohoo for quality assurance... woohoo for backups... woohoo for not using a database... woohoo for deployment... i was in the call with him it SHOULD work but its just not, I watched him test it and everything, we are trying to fix it, please dont spread misinformation |
|
|
|
Post by Polaris Seltzeris on May 26, 2020 23:43:38 GMT
Woohoo for quality assurance... woohoo for backups... woohoo for not using a database... woohoo for deployment... i was in the call with him it SHOULD work but its just not, I watched him test it and everything, we are trying to fix it, please dont spread misinformation Nobody is spreading misinformation, I'm observing that once again catastrophe has occurred after the production server was updated, no quality assurance yet again. |
|
|
|
Post by DragonSlayer2189 on May 26, 2020 23:45:25 GMT
i was in the call with him it SHOULD work but its just not, I watched him test it and everything, we are trying to fix it, please dont spread misinformation Nobody is spreading misinformation, I'm observing that once again catastrophe has occurred after the production server was updated, no quality assurance yet again. you said we werent using a database, we are, you said we didnt have quality assurance, we did, we have no clue why this isnt working because we tested it and it should work but its not |
|
|
|
Post by Polaris Seltzeris on May 26, 2020 23:49:00 GMT
Nobody is spreading misinformation, I'm observing that once again catastrophe has occurred after the production server was updated, no quality assurance yet again. you said we werent using a database, we are, you said we didnt have quality assurance, we did, we have no clue why this isnt working because we tested it and it should work but its not So you're telling me there's a QA server where the exact server is tested prior to it being deployed to prod? Because pretty sure if you did you would've been able to identify this issue before it would've ever made it to production. Typically databases don't just get reset which is what others on this thread have stated (and one called it a list which is not what a database is). Main point is, yet again a change to the server was rolled out without quality assurance, and yet again disaster has ensued despite all of the recommendations that have been put forth on QA and deployment. |
|
|
|
Post by DragonSlayer2189 on May 27, 2020 0:30:52 GMT
you said we werent using a database, we are, you said we didnt have quality assurance, we did, we have no clue why this isnt working because we tested it and it should work but its not So you're telling me there's a QA server where the exact server is tested prior to it being deployed to prod? Because pretty sure if you did you would've been able to identify this issue before it would've ever made it to production. Typically databases don't just get reset which is what others on this thread have stated (and one called it a list which is not what a database is). Main point is, yet again a change to the server was rolled out without quality assurance, and yet again disaster has ensued despite all of the recommendations that have been put forth on QA and deployment. there is a test server, and humman error happens. |
|
|
|
Post by DragonSlayer2189 on May 27, 2020 0:35:23 GMT
issue has been resolved can someone lock this, thx
|
|
|
|
Post by Polaris Seltzeris on May 27, 2020 0:41:41 GMT
So you're telling me there's a QA server where the exact server is tested prior to it being deployed to prod? Because pretty sure if you did you would've been able to identify this issue before it would've ever made it to production. Typically databases don't just get reset which is what others on this thread have stated (and one called it a list which is not what a database is). Main point is, yet again a change to the server was rolled out without quality assurance, and yet again disaster has ensued despite all of the recommendations that have been put forth on QA and deployment. there is a test server, and humman error happens. The whole point is to have a system to prevent human error, but clearly that isn't being attempted here. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 27, 2020 3:27:34 GMT
When big changes happen shit is expected to break, oh well. The issue is fixed and no data was lost. The whole point is to have a system to prevent human error, but clearly that isn't being attempted here. im sorry but ive never heard of any system to stop bugs from happening. |
|
[/spolier]